- From: <bugzilla@jessica.w3.org>
- Date: Mon, 25 Mar 2013 17:56:04 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20714
--- Comment #11 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
(In reply to comment #10)
> We could add the following attribute if you really want to be able to signal
> that
> HTMLMediaElement.seekable should return an empty TimeRanges.
> partial interface MediaSource {
> attribute boolean seekable;
> }
>
> - Initially set to true.
> - If true then existing behavior will be used.
> - If false then an empty TimeRanges object will be returned by
> HTMLMediaElement.seekable.
I think applications are going to want more control than seekable or not
seekable. As I said before, I don't think this is necessary as a v1 feature.
Applications can build custom UI with whatever seek logic they want. Once we
get more implementation experience of what people commonly want to build,
especially for the Live scenario, we can consider what platform support this
requires.
I recommend RESOLVE, LATER.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 25 March 2013 17:56:09 UTC