W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > April 2011

[Bug 12267] <video> Make video state transitions happen in the same task as firing events

From: <bugzilla@jessica.w3.org>
Date: Tue, 26 Apr 2011 08:31:53 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QEdgX-0001Qk-Ol@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #17 from Philip Jägenstedt <philipj@opera.com> 2011-04-26 08:31:48 UTC ---
(In reply to comment #15)
> As a developer I just know that when I take a peek at the readyState, it will
> be merely more than a Heisenberg measurement.

I think you meant "as the author of The Definitive Guide to HTML5 Video" ;-)
It's enough that 1% of web authors make a mistake and create scripts with race
conditions for this to be a serious problem, causing browsers with slightly
different timing to appear more broken than the ones that were tested.

> I am struggling to see the race conditions that are being used as a reason to
> make changes to state transitions here. Can you provide an example where the
> developer would get the wrong information? Or would get into an unsolvable
> situation?

It's almost always possible to work around the race conditions if you know
they're there. I listed some examples of problems that less-than-perfect
programmers could run into in
<http://lists.w3.org/Archives/Public/public-html-a11y/2011Apr/0232.html>.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 26 April 2011 08:31:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:08 UTC