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 21812 - [Custom]: Element upgrade does not perform initialization, but it should
Summary: [Custom]: Element upgrade does not perform initialization, but it should
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 18720
  Show dependency treegraph
 
Reported: 2013-04-24 14:01 UTC by Dominic Cooney
Modified: 2013-04-24 21:21 UTC (History)
0 users

See Also:


Attachments

Description Dominic Cooney 2013-04-24 14:01:42 UTC
The element upgrade algorithm goes as far as saying "For each item ELEMENT in CANDIDATES, set the value of the [[Prototype]] internal property of ELEMENT to PROTOTYPE".

This is very different to the element initialization algorithm, which will invoke lifecycle callbacks.

If a custom element author wanted to implement the equivalent of <video autoplay>, they would have to do manual tree walking to effect this for elements in the tree before document.register is called.
Comment 1 Dimitri Glazkov 2013-04-24 21:21:04 UTC
https://dvcs.w3.org/hg/webcomponents/
Comment 2 Dimitri Glazkov 2013-04-24 21:21:24 UTC
https://dvcs.w3.org/hg/webcomponents/rev/b6affe831db3