Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1].
This means specifically we do not throw an exception when the context node is
not HTML or SVG and if initially the context element is null, we follow step 2
to create an appropriate context element to be used in step 3.

Behavior matches Firefox and Safari.

BUG=616760
[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface

Committed: https://crrev.com/a695888f5a4372b346a2d9c2650c8d81e9a5434b
Cr-Commit-Position: refs/heads/master@{#420573}

[rwlbuis, 2016-09-21 23:21:14]

Description was changed from

==========
createContext Wip

BUG=
==========

to

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1]. This
means


Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface
==========

[rwlbuis, 2016-09-22 20:33:38]

Description was changed from

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1]. This
means


Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface
==========

to

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1]. This
means
specifically we do not throw an exception when the context node is not HTML or
SVG
and if initially the context element is null, we follow step 2 to create an
appropriate context element to be used in step 3.

Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface
==========

[rwlbuis, 2016-09-22 20:44:13]

Description was changed from

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1]. This
means
specifically we do not throw an exception when the context node is not HTML or
SVG
and if initially the context element is null, we follow step 2 to create an
appropriate context element to be used in step 3.

Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface
==========

to

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1].
This means specifically we do not throw an exception when the context node is
not HTML or SVG and if initially the context element is null, we follow step 2
to create an appropriate context element to be used in step 3.

Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface
==========

[rwlbuis, 2016-09-22 21:45:32]

rob.buis@samsung.com changed reviewers:
+ tkent@chromium.org

[rwlbuis, 2016-09-22 21:45:33]

PTAL. Note that this keeps the SVG behavior introduced for crbug.com/107982.

[tkent, 2016-09-22 23:36:57]

lgtm

[rwlbuis, 2016-09-23 01:01:19]

The CQ bit was checked by rob.buis@samsung.com

[commit-bot: I haz the power, 2016-09-23 01:02:11]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-23 04:03:06]

Description was changed from

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1].
This means specifically we do not throw an exception when the context node is
not HTML or SVG and if initially the context element is null, we follow step 2
to create an appropriate context element to be used in step 3.

Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface
==========

to

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1].
This means specifically we do not throw an exception when the context node is
not HTML or SVG and if initially the context element is null, we follow step 2
to create an appropriate context element to be used in step 3.

Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface
==========

[commit-bot: I haz the power, 2016-09-23 04:03:07]

Committed patchset #6 (id:90001)

[commit-bot: I haz the power, 2016-09-23 04:05:14]

Description was changed from

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1].
This means specifically we do not throw an exception when the context node is
not HTML or SVG and if initially the context element is null, we follow step 2
to create an appropriate context element to be used in step 3.

Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface
==========

to

==========
Update createContextualFragment behavior to latest spec

Update createContextualFragment behavior to latest spec listed under [1].
This means specifically we do not throw an exception when the context node is
not HTML or SVG and if initially the context element is null, we follow step 2
to create an appropriate context element to be used in step 3.

Behavior matches Firefox and Safari.

BUG=616760

[1] https://w3c.github.io/DOM-Parsing/#extensions-to-the-range-interface

Committed: https://crrev.com/a695888f5a4372b346a2d9c2650c8d81e9a5434b
Cr-Commit-Position: refs/heads/master@{#420573}
==========

[commit-bot: I haz the power, 2016-09-23 04:05:15]

Patchset 6 (id:??) landed as
https://crrev.com/a695888f5a4372b346a2d9c2650c8d81e9a5434b
Cr-Commit-Position: refs/heads/master@{#420573}