[Bug 20714] timestampOffset in live case

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20714

--- Comment #7 from Cyril Concolato <cyril.concolato@telecom-paristech.fr> ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #3)
> > > (In reply to comment #2)
> > > > Created attachment 1316 [details]
> > > > exemple of timeline after joining a live stream 2h after the start
> > > 
> > > Apps can draw whatever custom UI they like for the seek buffer. It's
> > > probably quite likely that apps with live content will want a custom UI
> > > indicating whether it is possible to seek back and by how much.
> > Why wouldn't it be possible for the app to indicate direclty to the built-in
> > UI that seek is not possible (either before the first data or outside of a
> > seeking window), without requiring custom UI?
> 
> Everything is possible if it is specified. There are lots of different
> options that people might want - our goal for v1 has been to keep it simple
> and address the most common goals intrinsically, gain implementation
> experience and see what is common in sites and libraries, and then consider
> enhancements subsequently.
I understand. Consider this bug report as a feedback from using the current
spec for live cases. I think enhancements are needed, whether or not they
should be part of v1 ... maybe.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 29 January 2013 15:26:08 UTC