W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] [html5] r3927 - [gow] (2) Update the rendering section to handle media elements' controls='' att [...]

From: Simon Pieters <simonp@opera.com>
Date: Mon, 21 Sep 2009 16:51:29 +0200
Message-ID: <op.u0l3j3djidj3kv@zcorpandell.linkoping.osa>
On Mon, 21 Sep 2009 12:22:03 +0200, <whatwg at whatwg.org> wrote:

> Author: ianh
> Date: 2009-09-21 03:22:02 -0700 (Mon, 21 Sep 2009)
> New Revision: 3927
>
> Modified:
>    index
>    source
> Log:
> [gow] (2) Update the rendering section to handle media elements'  
> controls='' attribute in a more correct way.
> Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7403


> Modified: source
> ===================================================================
> --- source	2009-09-21 10:05:44 UTC (rev 3926)
> +++ source	2009-09-21 10:22:02 UTC (rev 3927)
> @@ -84559,9 +84559,9 @@
>   <pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
> -[hidden], area, audio:not([controls]), base, basefont, command,
> -datalist, head, input[type=hidden], link, menu[type=context], meta,
> -noembed, noframes, param, rp, script, source, style, title {
> +[hidden], area, base, basefont, command, datalist, head,
> +input[type=hidden], link, menu[type=context], meta, noembed, noframes,
> +param, rp, script, source, style, title {
>    display: none;
>  }
> @@ -85576,13 +85576,16 @@
>    elements are expected to be treated as ordinary elements in the
>    rendering model.</p>
> -  <p>The <code>audio</code> element, when it has a <code
> -  title="attr-media-controls">controls</code> attribute, is expected
> -  to be treated as a replaced element about one line high, as wide as
> -  is necessary to expose the user agent's user interface features.</p>
> +  <p>The <code>audio</code> element, when it is <span title="expose a
> +  user interface to the user">exposing a user interface</span>, is
> +  expected to be treated as a replaced element about one line high, as
> +  wide as is necessary to expose the user agent's user interface
> +  features. When an <code>audio</code> element is not <span
> +  title="expose a user interface to the user">exposing a user
> +  interface</span>, it is expected to render as an empty element.</p>

Why did you change from display:none to an empty element? Browsers have  
already implemented it as display:none, and I think it's a nicer behavior  
for authors who want to style audio elements that expose controls (e.g.  
giving a border) without affecting audio elements without controls.

I suggest forcing display:none, like with <noscript>.


> -  <p>The <code>video</code> element's <code
> -  title="attr-media-controls">controls</code> attribute is not
> +  <p>Whether a <code>video</code> element is <span title="expose a
> +  user interface to the user">exposing a user interface</span> is not
>    expected to affect the size of the rendering; controls are expected
>    to be overlaid with the page content without causing any layout
>    changes, and are expected to disappear when the user does not need

-- 
Simon Pieters
Opera Software
Received on Monday, 21 September 2009 07:51:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC