- From: <bugzilla@jessica.w3.org>
- Date: Tue, 07 Jan 2014 20:47:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24226
Adrian Bateman [MSFT] <adrianba@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #1 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
The session close algorithm runs when the session actually closes. Prior to
that, the things that result in triggering the session close algorithm might
cause messages to be passed and the state change to PENDING first.
For example, the release() method says "or schedule other work that later
causes the session to be closed." This other work might be firing a message
event that sets the state to PENDING. Once the response is received, the
session close algorithm will run.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 7 January 2014 20:47:25 UTC