[Bug 22132] New: [imports]: 6 Loading Imports: It is not clear how PARSER and FRAGMENT relate each otehr

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

            Bug ID: 22132
           Summary: [imports]: 6 Loading Imports: It is not clear how
                    PARSER and FRAGMENT relate each otehr
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: morrita@google.com
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 20683

Seeing algorithm on "6 Loading Imports",
It seems the PARSER eats bytes from fetched resource.
But it isn't clear how parsed result is pushed into FRAGMENT.
Naively reading, the tree is built into the owner node, which is apparently
wrong.

Consequently, it isn't clear if which range of parsed document
the FRAGMENT should have. Should <html> be contained?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 22 May 2013 11:17:15 UTC