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 14:40:46 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qntfi-0000cU-Pq@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

--- Comment #42 from David Singer <singer@apple.com> 2011-08-01 14:40:45 UTC ---
(In reply to comment #41)
> (In reply to comment #40)
> 
> A concrete example of this would be Philip's example in comment #5:
> v.onloadstart = function() {
>   v.currentTime = 10;
> }

I think that we should be careful to make sure that program snippets such as
this stay unreliable; at a glance, it is obviously wrong, as previously
discussed. I think if you write obviously wrong code, you deserve unpredictable
behavior!

Overall, I agree with Ian; we need to make sure we have a 'cure' that is
actually better than the 'disease'.  Every time I look at the comments here,
and think about it, I end up concluding that freezing some values on script
entry merely moves the difficulties around - that it doesn't seem to reduce the
number of difficulties at all.

I'm open to hearing concrete suggestions, as I am all in favor of APIs where
'naive' simple usage is actually also the least likely to be buggy, but I am
having a hard time seeing what the consistent change is that actually leads to
improvement.

-- 
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 14:40:47 UTC

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