W3C home > Mailing lists > Public > public-html-a11y@w3.org > October 2012

[Bug 19277] Relationship and precedence of hidden="" and display:none should be clarified/defined

From: <bugzilla@jessica.w3.org>
Date: Thu, 04 Oct 2012 20:57:05 +0000
Message-Id: <E1TJsTh-0002fC-FD@jessica.w3.org>
To: public-html-a11y@w3.org

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
                 CC|                            |bzbarsky@mit.edu

--- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> 2012-10-04 20:57:05 UTC ---
This is already clearly defined in the specification.  Specifically,
http://dev.w3.org/html5/spec/single-page.html#hidden-elements defines a CSS

  [hidden] { display: none; }

says is:

  expected to be used as part of the user-agent level style sheet defaults for
  all documents that contain HTML elements.

Then http://www.w3.org/TR/CSS21/cascade.html#cascade defines how this interacts
with other CSS rules.

In particular, the TF's conclusion seems to be the exact opposite of what the
spec says right now, and of what UAs which implement @hidden interoperably
implement.  A testcase is at
http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=1815 and renders
identically in Presto, Gecko, and WebKit.  Trident does not seem to support
@hidden at all (tested IE9 and IE10).

As an implementor, I would object to breaking web compat and compat with other
implementations here by changing the behavior.

Configure bugmail: https://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 Thursday, 4 October 2012 20:57:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:31 UTC