- From: <bugzilla@jessica.w3.org>
- Date: Mon, 09 Nov 2015 21:37:41 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29271
Matt Wolenetz <wolenetz@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #1 from Matt Wolenetz <wolenetz@google.com> ---
nikolay.dimitrov@viblast.com: Thank you for reporting this. We have recently
moved the bug tracking for MSE to github
(https://github.com/w3c/media-source/issues). Especially, please see
https://github.com/w3c/media-source/issues/5 and comment on that issue whether
or not the proposed solution would satisfy your concerns mentioned on this bug.
In the meantime, I will close this bugzilla bug. If you deem your concerns to
be distinct enough from https://github.com/w3c/media-source/issues/5, please
file a new github issue for the MSE spec.
With respect to maintaining a custom UI/seeking bar, that may still be required
of apps for best UX, even if there is an API for modifying the seekable
range(s) of an MSE-attached HTMLMediaElement. However, ability of the app to
specify range(s) to which MSE seeks must be clamped in a standardized fashion
was indeed deemed to be a useful MSE v.1 feature, and such specification is
tracked in https://github.com/w3c/media-source/issues/5.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 9 November 2015 21:37:43 UTC