- From: <bugzilla@jessica.w3.org>
- Date: Wed, 06 Apr 2011 12:00:15 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11981 --- Comment #4 from Philip Jägenstedt <philipj@opera.com> 2011-04-06 12:00:13 UTC --- Another example of event raciness that I just stumbled upon: We had a test for checking the order of events in for preload=metadata. In the loadstart event handler, event handler for 'progress', 'suspend', 'abort', 'error', 'loadedmetadata', 'loadeddata', 'canplay', and 'canplaythrough' were registered, but it depends on chance which of these have already been fired. In our case, we missed the first progress event, but got the rest. Of course it's possible to write code to avoid the race conditions, but if we as browser developers accidentally do things like this, then we can be 100% sure that web authors will also inadvertently come to depend on the most common outcome of race conditions in common browsers. -- 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 Wednesday, 6 April 2011 12:00:18 UTC