- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Jun 2011 23:45:03 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11981 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-06-02 23:45:03 UTC --- > This problem was found when someone was trying to develop an extension to stop > media elements from autoplaying. That's something that should be done natively by the UA. If an extension is actually going to do this, it should be done from mutation events (or their brethren), long before 'loadstart' fires. We can't do what comment 1 suggests since that would block autoplay behaviour if there was another task running (e.g. with an alert()). Comment 4 seems to be a separate issue. That issue is present across the Web platform, it's not unique to <video>. We can't gate the processing of video on whether JS has handled the previous step, that would just kill performance in any case where there was a high load. 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 aboe -- 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:45:05 UTC