[Bug 24862] New: Disabling Subtitles Based on Users Changing Preferences in the UA

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

            Bug ID: 24862
           Summary: Disabling Subtitles Based on Users Changing
                    Preferences in the UA
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: CR HTML5 spec
          Assignee: robin@w3.org
          Reporter: hbbtvjon@gmail.com
        QA Contact: public-html-bugzilla@w3.org
                CC: public-html-admin@w3.org

This issue is raised on behalf of HbbTV - see http://www.hbbtv.org, an
organisation specifying the use of web technologies in television receivers.
HbbTV is in the process of adding the HTML5 video element to its specification.
The current HbbTV specification uses the <object> element for presenting video
in an HTML page.

One of the steps in the description of automatic text track selection is the
following;

http://www.w3.org/TR/html5/embedded-content-0.html#honor-user-preferences-for-automatic-text-track-selection

"3. If any of the text tracks in candidates have a text track mode set to
showing, abort these steps.".

As mentioned in issue #24860, TV receivers include a UI to enable the user to
set and change preferences relating to subtitles/closed captions. The subtitle
UI in a TV receiver almost always permits the end-user to disable as well as
enable subtitles.

The text from "honor user preferences" above can be interpreted as meaning that
the "Honor user preferences for automatic text track selection for this
element" process can never result in subtitles that were showing becoming
hidden.

We would appreciate your feedback on whether a mechanism in the user agent to
permit the end-user to disable subtitles is compatible with the definition of
"Honor user preferences".

If such a mechanism is not compatible with "Honor user preferences", can this
be changed?

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

Received on Friday, 28 February 2014 15:58:11 UTC