[Bug 29166] New: Fragment serializing algorithm has wrong behaviour for passing node

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

            Bug ID: 29166
           Summary: Fragment serializing algorithm has wrong behaviour for
                    passing node
           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: ---

This algo doesn't fit for getter innerHTML/outerHTML in XML case:
http://www.w3.org/TR/DOM-Parsing/#dfn-concept-fragment-serializing-algorithm

If I correct then we have:

- for innerHTML algo try serializing passed context object, but should operate
only on its childs (what we see in HTML fragment serialization algorithm: "This
algorithm serializes the children of the node being serialized, not the node
itself.")

http://www.w3.org/TR/DOM-Parsing/#widl-Element-innerHTML
"On getting, return the result of invoking the fragment serializing algorithm
on the context object providing true for the require well-formed flag (this
might throw an exception instead of returning a string)."

- for outerHTML you pass some "fictional node", but what is this (has
namespace, has owner document?) and how the algorithm should handle it? This
term is not too general, even for HTML fragment serialization algorithm (which
accepts only Element, Document, or DocumentFragment)?

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

Received on Thursday, 1 October 2015 13:38:45 UTC