- From: <bugzilla@jessica.w3.org>
- Date: Wed, 24 Apr 2013 14:01:42 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21812
Bug ID: 21812
Summary: [Custom]: Element upgrade does not perform
initialization, but it should
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Component Model
Assignee: dglazkov@chromium.org
Reporter: dominicc@chromium.org
QA Contact: public-webapps-bugzilla@w3.org
Blocks: 14968
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 24 April 2013 14:01:45 UTC