- From: <bugzilla@jessica.w3.org>
- Date: Fri, 05 Oct 2012 18:05:36 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19277
Tab Atkins Jr. <jackalmage@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jackalmage@gmail.com
--- Comment #8 from Tab Atkins Jr. <jackalmage@gmail.com> 2012-10-05 18:05:36 UTC ---
(In reply to comment #2)
> This is already clearly defined in the specification. Specifically,
> http://dev.w3.org/html5/spec/single-page.html#hidden-elements defines a CSS
> rule:
>
> [hidden] { display: none; }
>
> that
> http://dev.w3.org/html5/spec/single-page.html#the-css-user-agent-style-sheet-and-presentational-hints
> 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.
Boris, what would you think about shifting the rule to be "display: none
!important;"? Whenever I've used hidden, I've put that rule in my stylesheet,
because otherwise I have to code defensively to avoid "un-hiding" things
accidentally.
--
Configure bugmail: https://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, 5 October 2012 18:05:38 UTC