- From: <bugzilla@jessica.w3.org>
- Date: Tue, 25 Jun 2013 07:06:53 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22446
Bug ID: 22446
Summary: [Custom]: Commentary about lifecycle callbacks queue
being empty when document.register is invoked is
incorrect
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 spec has this informative language:
"Also, because of when lifecycle callbacks are added to the lifecycle callbacks
queue, the queue should be empty when document.register is invoked."
I don't think it is true; consider this case:
<script>
var A = document.register('x-a', ...);
// callbacks have been exhaustively invoked by register() at this point
var x = new A();
// ready has been eagerly invoked by the constructor at this point
document.body.appendChild(x);
// inserted(x) is queued at this point
// queue is NOT empty
document.register('x-b', ...);
</script>
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 25 June 2013 07:06:55 UTC