[Bug 29174] New: ProcessingInstruction node is correct (as context) for Range.createContextualFragment() method

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29174

            Bug ID: 29174
           Summary: ProcessingInstruction node is correct (as context) for
                    Range.createContextualFragment() method
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM Parsing and Serialization
          Assignee: travil@microsoft.com
          Reporter: crimsteam@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org
  Target Milestone: ---

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?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Saturday, 3 October 2015 01:03:40 UTC