[webcomponents] [Custom]: make callbacks more explicit (bugzilla: 24579) (#186)

Title: [Custom]: make callbacks more explicit (bugzilla: 24579)

Migrated from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24579

----
comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24579#c0
*Anne* wrote on 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.

----

comment: 1
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24579#c1
*Anne* wrote on 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.

----

comment: 2
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24579#c2
*Dimitri Glazkov* wrote on 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?

----

comment: 3
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24579#c3
*Dimitri Glazkov* wrote on 2014-10-27 17:34:02 +0000.

*** Bug 27179 has been marked as a duplicate of this bug. ***

----

comment: 4
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24579#c4
*Anne* wrote on 2014-10-27 17:42:42 +0000.

(Currently Web IDL offers no way for other specifications to define extended attributes.)

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/186