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 15551 - Consider attribute forwarding
Summary: Consider attribute forwarding
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:16 UTC by Dimitri Glazkov
Modified: 2013-07-17 16:40 UTC (History)
1 user (show)

See Also:

Attachments

Description Dimitri Glazkov 2012-01-13 23:16:56 UTC 
In our discussion with Neil and Jonas, the topic of attribute forwarding came up. They are present in XBL and specified in XBL2 (http://dev.w3.org/2006/xbl2/#attribute-forwarding), but I was trying to avoid them, opting for imperative-only approach with an attributeChanged callback.

I am still not sold we need them, because they are a bit magical and the XBL2 spec gets pretty funky with them.

However, Jonas pointed out that there might be a need for them, because they would provide a way to synchronously signaling into a shadow DOM subtree without involving Javascript callbacks (that we would _need_ to make async for sanity reasons).
Comment 1 Dimitri Glazkov 2013-07-17 16:40:07 UTC 
The attributeChangedCallback provides all the necessary functionality. Closing this.