[Bug 24860] When can user agents honor the user preferences for automatic text track selection

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

--- Comment #5 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
(In reply to Jon Piesing (HbbTV) from comment #4)
> The URL given doesn't work. Is this a reference to section 4.7.10.13 "User
> interface" and the controls attribute?

Try this one:
http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#expose-a-user-interface-to-the-user

> If it's a reference to the controls attribute then that has numerous issues
> in a TV environment. TV apps generally do not include the controls attribute
> to avoid those issues and the subtitle key would need to work when that
> attribute is not present.


To avoid what issues?

I don't understand. How can you have UA provided controls when you disallow the
@controls attribute?

Also, if you disallow the browser from creating controls, but then provide your
own on top, then it's up to you to expose such a user interface and take care
of the providing the features that the @controls attribute would provide. "You"
being whatever interface you are adding in top of the browser. If there is some
sort of "middleware" that provides remote control mapping to the browser, but
is not part of what you call an "application", then its up to that part to make
sure that the right tracks are activated/deactivated. From the HTML spec's
point of view, that's still an "application".


> >In particular, when toggling subtitles on/off, the browser will set the "text track mode" of all subtitles tracks to "disabled" and thus in the "time marches on" algorithm, all disabled tracks cues will not be shown.
> 
> That is great but doesn't address the point of whether a browser mechanism
> to control subtitles is permitted when the controls attribute is not
> present.

Of course it is. The section that I referred to explicitly says:

"If the attribute is present, or if scripting is disabled for the media
element, then the user agent should expose a user interface to the user. "

Notice that it explicitly mentions "scripting is disabled" as another situation
when the browser should expose a UI.

The issue here is that with HTML pages and video elements that have no
@controls attribute, you might find that the page author has created the
controls through JavaScript and is rendering them on top of the video elements.
I don't know how you want to handle that in the set-top box case. Do you want
to disable such controls and render some default controls of the TV that
include the remote control access? Or do you want to have the remote control
also activate/deactivate the subtitles? Both is possible. Neither is disallowed
in the spec.

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

Received on Monday, 3 March 2014 00:56:20 UTC