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 15552 - [Custom Elements]: Consider adding in-tree/out-of-tree callbacks to custom elements
Summary: [Custom Elements]: Consider adding in-tree/out-of-tree callbacks to custom el...
Status: RESOLVED FIXED
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
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 18511
  Show dependency tree / graph
 
Reported: 2012-01-13 23:20 UTC by Dimitri Glazkov
Modified: 2013-05-20 19:26 UTC (History)
2 users (show)

See Also:

Attachments

Description Dimitri Glazkov 2012-01-13 23:20:05 UTC 
Neil pointed out several cases where setup/cleanup work must be done to maintain state integrity of complex widgets (such as selected item in a menu), when one part of the widget is removed from the tree.
Comment 1 Dominic Cooney 2012-05-22 02:00:17 UTC 
Doesn’t maintaining that state require synchronous notification? How do you avoid getting back to the hated mutation events? I suppose you could try to write some declarative constraints on the shape of the tree?
Comment 2 Dimitri Glazkov 2013-05-20 19:26:39 UTC 
This was added to spec.