- From: <bugzilla@jessica.w3.org>
- Date: Fri, 15 Jul 2011 22:00:20 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267 --- Comment #35 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-07-15 22:00:17 UTC --- (In reply to comment #34) > The problem that when an event fires, there are no guarantees about what state > the element is actually in There is no way we can fix this in a non-confusing way. For example, say that a 'timeupdate' event fires and currentTime is t=5. The script sets a cue with pauseOnExit set for a time of t=6. But really, the time when the script does this is t=7. Are you saying we should somehow warp the video back to t=6 and pause? What about a script that tries to fast-forward by 5 each time it is invoked. The script is invoked at t=1, but by the time the script is ready to do the fast-forward, it's actually at t=7, such that the user actually sees the script go _backwards_ rather than jumping forwards. I don't understand why authors would find it intuitive that new Date() is consistent with reality but video.currentTime or video.readyState is not. Could you enumerate exactly which features you think should be pinned? -- 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 Friday, 15 July 2011 22:00:25 UTC