23069 2013-08-26 16:15:42 +0000 [Custom]: Elements in HTML Imports should upgrade as if imports blocked parsing 2013-08-26 16:50:11 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Windows NT RESOLVED DUPLICATE 22928 P2 normal --- 14968 1 sorvell dglazkov public-webapps-bugzilla oldest_to_newest 92578 0 sorvell 2013-08-26 16:15:42 +0000 Consider a custom element that declares other custom elements. See, for example, <polymer-element> (https://github.com/Polymer/polymer) which is similar to the deprecated <element> element. It's common to want to place dependencies in HTML Imports. Consider this setup: main document: <script src="polymer.js"></script> // registers polymer-element <link rel="import" href="x-a.html"> <polymer-element name="x-b" extends="x-a">...</polymer-element> x-a.html: <polymer-element name="x-a">...</polymer-element> In this case, because HTML Imports are non-blocking, the import will parse after the main document and the definition for x-a will not be available by the time x-b wants to extend it. Ideally, in the presence of HTML Imports custom elements would upgrade in the same order as if imports were blocking (e.g. polymer-element x-a upgrades before polymer-element x-b). Although placing the script element after the x-a import would also address this use case, it would be unfortunate if this were required because it makes loading the import block parsing the main document. 92580 1 dglazkov 2013-08-26 16:46:57 +0000 This is a dupe of bug 22928, right? 92581 2 sorvell 2013-08-26 16:48:47 +0000 Yup, dupe. Sorry didn't see the other bug. 92582 3 dglazkov 2013-08-26 16:50:11 +0000 *** This bug has been marked as a duplicate of bug 22928 ***