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

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 15 Jul 2011 21:41:14 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qhq8I-0008FS-W7@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13275

Shelley Powers <shelleyp@burningbird.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |shelleyp@burningbird.net

--- Comment #2 from Shelley Powers <shelleyp@burningbird.net> 2011-07-15 21:41:14 UTC ---
(In reply to comment #1)
> (In reply to comment #0)
> > 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. 
> 
> The attribute is not added.  The controls are simply displayed, which happens
> to be the same thing that occurs if you set the attribute.
> 
> 

Point taken. 

OK, then I'm not aware of other cases where the browsers change the web page
elements on their own when scripting is disabled -- other than implementing
noscript. 

> > 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.
> 
> Disabling the control UI when there is no possibility of providing custom
> controls is almost certainly going to be done accidentally, by an author
> assuming that scripting is always on and their script-based controls will be
> added, and so just omitting the @controls attribute.

But we've always had this problem. 

Does the browser then automatically display a hidden section when scripting is
disabled? Does it automatically un-collapse a div element when scripting is
disabled? So what is it about the video or audio element that requires a
complete change to the programming paradigm we've lived with for over 15 years?

And what about the cases where the author or developer does not want the UI to
display? For whatever reason?

This is changing the web page when scripting is disabled, and in such a way
that the developer or author has absolutely no control over this change.

-- 
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 Friday, 15 July 2011 21:41:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:13 UTC