- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Nov 2014 17:57:06 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27420 --- Comment #3 from Domenic Denicola <d@domenic.me> --- (In reply to Boris Zbarsky from comment #2) > There's a timing difference here, right? The current cloning steps behavior > means there are never script-exposed elements that don't have the relevant > state propagated yet, while using clonedCallback for this would mean there > are. I don't think so? Note that how custom element callbacks work is that they're copied to an internal registry when you do document.registerElement; it doesn't do a run-time lookup of `theElement.clonedCallback`. So if you envision this as HTML "registering" all its elements ahead of time, the cloned callbacks would be registered with the system ahead of time and couldn't be intercepted or messed with. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 24 November 2014 17:57:13 UTC