- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Jun 2011 23:00:43 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #28 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-06-02 23:00:40 UTC --- Doing what comment 0 suggests doesn't fix the code in comment 5: > var v = document.createElement('video'); > v.onloadstart = function() { > v.currentTime = 10; > } > v.src = 'video.webm'; ...as there's no state being read here. We can't possibly make the API work according to frozen state rather than current state, imagine what would happen if there was a task that alert()ed, then the video ended, then the script called play()... do you want to have to remember that the video was playing, so play() should do nothing, even though now the video has finished, so really it should restart? What about if the script got the "buffered" TimeRange before the alert(), then seeked into one after the alert(), but in the meantime the browser had to dispose of the particular part of the buffer? Do you just seek to the given time anyway and play elevator music while you desperately try to rebuffer the video without letting the script know that the data it got from the API was actually out of date? That way lies even more madness than having race conditions. If there are specific high-risk cases where we can make things more stable, I'm certainly open to ideas, but I don't think generally freezing everything is a viable solution. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: see above -- 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 Thursday, 2 June 2011 23:00:45 UTC