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

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 01 Aug 2011 00:10:52 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qng5s-0005XT-TE@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #41 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2011-08-01 00:10:50 UTC ---
(In reply to comment #40)
> On the other hand, breakpoints and
> single-step debugging are often quite useless for finding and fixing bugs in
> code dealing with asynchronous state changes; a more snapshotting approach can
> actually *aid* breakpoint-based debugging because if you hit a breakpoint,
> execution will continue after the breakpoint the same as if you hadn't stopped
> in the breakpoint. Changing behavior when you add breakpoints sucks!

A concrete example of this would be Philip's example in comment #5:
v.onloadstart = function() {
  v.currentTime = 10;
}
With the current model, this would often work but sometimes fail. Let's
optimistically assume that the developer can reproduce the bug. So they set a
breakpoint on "v.currentTime = 10". The breakpoint gets hit. The developer
single-steps. Now the assignment to v.currentTime succeeds because the metadata
was loaded during the significant delay between the breakpoint being hit and
the developer hitting the single-step button.

-- 
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 Monday, 1 August 2011 00:10:54 UTC

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