This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22132 - [imports]: 6 Loading Imports: It is not clear how PARSER and FRAGMENT relate each otehr
Summary: [imports]: 6 Loading Imports: It is not clear how PARSER and FRAGMENT relate ...
Status: RESOLVED INVALID
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20683
  Show dependency tree / graph
 
Reported: 2013-05-22 11:17 UTC by Morrita Hajime
Modified: 2013-07-18 21:32 UTC (History)
0 users

See Also:

Attachments

Description Morrita Hajime 2013-05-22 11:17:14 UTC 
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?
Comment 1 Dimitri Glazkov 2013-07-18 21:32:23 UTC 
Now that we're using documents again, this is moot.