- From: <bugzilla@jessica.w3.org>
- Date: Sat, 25 Jan 2014 00:42:42 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17750
David Dorwin <ddorwin@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #25 from David Dorwin <ddorwin@google.com> ---
Do we need to explicitly handle release() being called in the CREATED state?
createSession(), loadSession(), and release() all schedule tasks to do their
work. Are these tasks required to run serially? (If so, does the spec need to
be more explicit about this or is this implied by "schedule a task"?) If not,
the createSession() task may not complete before release() is called.
It may actually be that we need to handle this in createSession() and
loadSession() by adding a condition to check for a release as the first
condition in the last substep of the "Schedule a task" step.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 25 January 2014 00:42:43 UTC