- From: <bugzilla@jessica.w3.org>
- Date: Thu, 08 Jan 2015 17:12:04 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27762 --- Comment #9 from Dimitri Glazkov <dglazkov@chromium.org> --- (In reply to Anne from comment #8) > (In reply to Gabor Krizsanits from comment #7) > > Can we agree on the before/after part real quickly? (Both for the > > from-the-map-removal and for the flag unsetting) > > I would go with before: > > * Unset the unresolved flag. > * Change the prototype. > * Remove from the map. > * Call the callback. Sounds about right, except map removal happens earler. Here's the detailed view of how I am planning to amend the spec: NEW: When creating a custom tag or type extension: * Set the flag EXISTING: When upgrading as part of registration (http://w3c.github.io/webcomponents/spec/custom/#dfn-element-registration-algorithm, step 7): * Enqueue "createdCallback" * Remove from the map (step 4 in http://w3c.github.io/webcomponents/spec/custom/#dfn-element-upgrade-algorithm) NEW: Just before "createdCallback" is invoked, in http://w3c.github.io/webcomponents/spec/custom/#dfn-element-registration-algorithm: * Unset the flag as first step. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 8 January 2015 17:12:06 UTC