- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Mon, 20 Dec 2010 02:14:52 +0100
- To: Media Fragment <public-media-fragment@w3.org>
Hi Everyone, the Media Fragment URI bug for HTML5 has been rejected again, even if only partially. We need to register some more bugs around it. I just wanted to bring it into the discussion this week. Cheers, Silvia. ---------- Forwarded message ---------- From: <bugzilla@jessica.w3.org> Date: Thu, Dec 16, 2010 at 9:35 AM Subject: [Bug 10723] support for media fragment URIs in relevant HTML5 elements To: silviapfeiffer1@gmail.com http://www.w3.org/Bugs/Public/show_bug.cgi?id=10723 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-12-16 08:35:31 UTC --- That's still two issues. Please only file one issue per bug. An issue is the atomic unit of complaint that one could have. If you find yourself writing a numbered list, you almost certainly have more than one issue. For comment 10 issue 1: the spec already says as much as it needs to say on the subject: "If either the media resource or the address of the current media resource indicate a particular start time, then set the initial playback position to that time and then seek seek to that time." (in the resource fetch algorithm) For comment 10 issue 2: that's a browser UI issue and out of scope of specs such as HTML. I suspect the same applies to many, if not all, of the other issues listed in comment 5, but I haven't studied them in detail. 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 reported the bug.
Received on Monday, 20 December 2010 01:15:46 UTC