- From: <bugzilla@jessica.w3.org>
- Date: Tue, 13 Aug 2013 00:00:17 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22928
Bug ID: 22928
Summary: [Custom]: Callbacks timing and HTML Imports
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Component Model
Assignee: dglazkov@chromium.org
Reporter: dglazkov@chromium.org
QA Contact: public-webapps-bugzilla@w3.org
CC: dominicc@chromium.org, sorvell@chromium.org
Blocks: 14968
This feature is probably more relevant to custom elements than imports, so
putting it into custom elements pile.
Consider this situation:
x-foo.html:
<polymer-element name="x-bar">
...
index.html:
<script> document.register('polymer-element', ...
...
<link rel=import href="x-foo.html">
...
<x-foo></x-foo>
The desired created callback order here is:
polymer-element
x-foo
However, since imports are loaded asynchronously, it's pretty likely that the
order will actually be:
x-foo
polymer-element
... which will result in sadness (polymer-element registers x-foo).
It smells like we need some sort of extra-ordering to callbacks for imports?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 13 August 2013 00:00:18 UTC