- From: <bugzilla@jessica.w3.org>
- Date: Fri, 07 Jun 2013 02:15:55 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22305 Bug ID: 22305 Summary: [imports]: Imports should be represented as Documents, not DocumentFragments. 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 Imports are inherently documents and representing it as DocumentFragment makes the specification unnecessarily complicated: - It is not clear how URLs of sub-imports are resolved. If you read it literally, it should be resolved against the URL of the master document. But people will expect it being done against parent document, which is stored as a DocumentFragment (that doesn't have any URL.) - Concurrent parsing could become tricky since there is single document which is the master. The spec should be written carefully not to expose the nature of this serial nature and ensure UA to be able to go parallel. - DocumentFragment doesn't have many convenient APIs that Document has. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 7 June 2013 02:16:00 UTC