This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24579 - [Custom]: make callbacks more explicit
Summary: [Custom]: make callbacks more explicit
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
: 27179 (view as bug list)
Depends on:
Blocks: 14968 20567
  Show dependency treegraph
Reported: 2014-02-07 11:00 UTC by Anne
Modified: 2015-07-06 08:13 UTC (History)
8 users (show)

See Also:


Description Anne 2014-02-07 11:00:05 UTC
"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 as that makes it much more explicit when everything happens relative to each other.
Comment 1 Anne 2014-02-07 11:01:53 UTC
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 Dimitri Glazkov 2014-05-09 20:32:46 UTC
I was just reading up on 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:
Comment 3 Dimitri Glazkov 2014-10-27 17:34:02 UTC
*** Bug 27179 has been marked as a duplicate of this bug. ***
Comment 4 Anne 2014-10-27 17:42:42 UTC
(Currently Web IDL offers no way for other specifications to define extended attributes.)
Comment 5 Hayato Ito 2015-07-06 08:13:55 UTC
Moved to