W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13624] New: The pause-on-exit flag should lead to the paused for user interaction state

From: <bugzilla@jessica.w3.org>
Date: Wed, 03 Aug 2011 19:37:03 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13624-2486@http.www.w3.org/Bugs/Public/>

           Summary: The pause-on-exit flag should lead to the paused for
                    user interaction state
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: a11y, a11ytf, media
          Severity: normal
          Priority: P2
         Component: LC1 HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: mstm@jp.ibm.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, public-html-a11y@w3.org

Section affected:

In the current cue processing algorithm, a cue whose pause-on-exit flag is set
causes the normal paused state when the cue stops being relevant. However,
since the pause-on-exit flag can be used only by the system for a certain
special purpose, this flag should cause the "paused for user interaction" state
rather than the normal paused state, so that the state can be controlled only
through a special interface, not thorough the normal pause/resume interface.

For example, for extended video descriptions which is a promising use case of
the pause-on-exit flag as discussed in the a11y task force (
http://lists.w3.org/Archives/Public/public-html-a11y/2011Jun/0065.html ), the
paused state needs to be controlled through accessibility APIs while it should
not be affected by the user's pause/resume operations.

Configure bugmail: http://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 Wednesday, 3 August 2011 19:37:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:59 UTC