- From: <bugzilla@jessica.w3.org>
- Date: Wed, 22 May 2013 20:32:05 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20189 --- Comment #6 from Daniel Buchner <danieljb2@gmail.com> --- I don't see how we get out of offering an event, consider the following: What happens when someone implements and registers their tag definition with purely imperative code via a <script> included in original source or any script piped in that is late-firing? If I register an element with document.register within a script, am I to presume there is no event to let me know when that code has upgraded all the nodes in the document that match the definition? If so, this could be a significant landmine for developers. My suggestion would be to fire one 'CustomElementsUpgraded' event for each *type* of element declared (which would contain an 'elementName' property) when all elements of that type present in the DOM have been upgraded. This would allow developers to know when elements are OK to touch regardless of which declaration route they opt for, or how 'late' they register an element. Make sense? Let me know if I'm explaining the problem/solution clearly. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 22 May 2013 20:32:10 UTC