24579 2014-02-07 11:00:05 +0000 [Custom]: make callbacks more explicit 2015-07-06 08:13:55 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED MOVED P2 normal --- 14968 20567 1 annevk dglazkov bzbarsky cam eoconnor mike mjs public-webapps rniwa wchen public-webapps-bugzilla oldest_to_newest 100001 0 annevk 2014-02-07 11:00:05 +0000 "Any time a script calls a method, reads or sets a property that is implemented by the user agent, the following actions must occur: " This needs to become part of the actual algorithms such as innerHTML, cloneNode(), etc. The easiest way to do that is tying it to IDL I think just as is done in the Chrome implementation. I recommend working with heycam on doing that per my outline in http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0142.html as that makes it much more explicit when everything happens relative to each other. 100003 1 annevk 2014-02-07 11:01:53 +0000 Note that we also need this mechanism for callbacks implemented by the user agent. E.g. when adoption happens we want to queue a callback that runs before the method that caused the adoption to return and mangles prototypes. 105577 2 dglazkov 2014-05-09 20:32:46 +0000 I was just reading up on extended attributes: http://heycam.github.io/webidl/#idl-extended-attributes. A simple ExtendedAttributeNoArgs thingy should suffice in this case -- something like [InvokesCustomElementCallbacks] or [ProcessesCustomElementCallbacks] or [ElementCallbackBarrier]? Heycam, should I just write this down in custom elements spec, or should it be part of Web IDL spec, like ES-specific attributes: http://heycam.github.io/webidl/#es-extended-attributes? 113790 3 dglazkov 2014-10-27 17:34:02 +0000 *** Bug 27179 has been marked as a duplicate of this bug. *** 113792 4 annevk 2014-10-27 17:42:42 +0000 (Currently Web IDL offers no way for other specifications to define extended attributes.) 121721 5 hayato 2015-07-06 08:13:55 +0000 Moved to https://github.com/w3c/webcomponents/issues/186