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

[Bug 13275] New: Display of media control UI when scripting is disabled

From: <bugzilla@jessica.w3.org>
Date: Fri, 15 Jul 2011 20:41:37 +0000
To: public-html@w3.org
Message-ID: <bug-13275-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13275

           Summary: Display of media control UI when scripting is disabled
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: shelleyp@burningbird.net
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Currently, as the HTML5 is defined, if a person does not provide the controls
attribute for whatever reason, and are using the autoplay functionality to
start a video when the page loads, if scripting is disabled, the user agents
are supposed to expose the control UI to the user. 

This means that the web page author/developer has no control over the display
of this control if scripting is disabled. 

I'm not aware of any other case where an element attribute is added into the
page when scripting is disabled. If the developer is unaware that this happens
when scripting is disabled, they may remain totally unaware that the control UI
is being displayed whenever the user accesses the page with scripting disabled. 

More importantly, they're not given the option to not have the control UI
display. 

The controls attribute is a boolean attribute, which means when its present,
display the control UI. It's reasonable to assume, then, that when it isn't
present, the author or developer does not want the control UI to be present. 

By enabling the control UI when the attribute is not listed and scripting is
disabled, the HTML5 specification is making it impossible to not have a control
UI whether the author wants one or not. This limits the choices available to
the author or developer.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 15 July 2011 20:41:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:36 GMT