29174 2015-10-03 01:03:36 +0000 ProcessingInstruction node is correct (as context) for Range.createContextualFragment() method 2015-10-03 01:03:36 +0000 1 1 1 Unclassified WebAppsWG DOM Parsing and Serialization unspecified PC Windows NT NEW P2 normal --- 1 crimsteam travil mike www-dom public-webapps-bugzilla oldest_to_newest 123464 0 crimsteam 2015-10-03 01:03:36 +0000 In algo for Range.createContextualFragment() method: http://www.w3.org/TR/DOM-Parsing/#dfn-dom-range-createcontextualfragment ProcessingInstruction node should not be forbidden as context, DOM4 prevents only DocumentType when setting range's start/end node: http://www.w3.org/TR/dom/#concept-range-bp-set and browsers (Firefox, Chrome, IE11) not throw for ProcessingInstruction. This node probably should be treat the same as Text and Comment. BTW, will be better changing variable names to something more obvious (what whe have for other methods): - passing argument /fragment/ to /text/ or /str/ (step 1) - /fragment node/ to /fragment/ (step 3/4/5) - and maybe /element/ to /context/ (like whe have for insertAdjacentHTML) - correct IDL and green box too One more thing, tables with Parameter/Type/Nullable/Optional are necessary? The same infos we see directly in IDL, so why repeat and unnecessarily making spec bigger?