W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2012

[Bug 14104] <track> Live captioning

From: <bugzilla@jessica.w3.org>
Date: Mon, 06 Feb 2012 12:17:49 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RuNW1-0007YT-2C@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14104

--- Comment #34 from Philip J <philipj@opera.com> 2012-02-06 12:17:42 UTC ---
(In reply to comment #33)
> (In reply to comment #32)
> > (In reply to comment #30)
> > > 
> > > LIVE--> rollup-size:3
> > > <00:00:00.000> I ma hnugry <00:00:05.000> <redoline> I am hungry
> > > 
> > > So, when you seek back to any time between 0 and 5 sec, you display the "I ma
> > > hnugry" text again, and for any time after 5 sec, you display the "I am hungry"
> > > text. This is what I mean by "replay everything exactly how it was received".
> > 
> > That seems like a net worse user experience than only showing the
> > correctly-spelt text.
> 
> I think it's unfaithful to have the browser make changes to the presentation
> when seeking back to it. What if the viewer has just seen something funny being
> typed and wants to rewind to it to show his friend who missed? 
> 
> I think we should leave such changes up to a content editor who is going to
> re-publish the live streamed video & captions with improvements, be that fixes
> to the video, or fixes to the captions.

If so, what should the in-memory model be? What do you see via the DOM APIs?

-- 
Configure bugmail: https://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 Monday, 6 February 2012 12:17:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 February 2012 12:17:59 GMT