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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19277

--- Comment #28 from James Craig <jcraig@apple.com> ---
(In reply to Leif Halvard Silli from comment #27)
> (In reply to James Craig from comment #26)
> > (In reply to Leif Halvard Silli from comment #25)
> > 
> > > Per HTML5 it is already an authoring error to make an element with the
> > > @hidden attribute visible. Citing the NOTE i HTML51: 
> > > 
> > > “Authors therefore have to take care when writing their style sheets to make
> > > sure that the attribute is still styled as expected.”
> > 
> > That's a note, not a normative statement. To the author "as expected" could
> > mean, "I do expect it to be visible even though it's marked as hidden." The
> > PF members were asking for this to throw an error or warning even if that's
> > what the author expected/intended.
> 
> (FWIW, I pondered citing the preceding paragraph, but cited the NOTE since
> the word "authors" occurred there.)
> 
> It is a note. But is not a "non-normative note". It is an explanation of the
> preceding non-note paragraph, which describes what @hidden is to be used
> for. I can hardly see that it is in line with the described purpose to
> render elements with @hidden visible. 


One of the normative statements:

> User agents should not render elements that have the hidden attribute specified. 

...would then be in violation with the current implementations, which allow
this content to be rendered via author styles. If this is a normative
statement, why not add the !important directive to avoid the cases listed in
comment #12?


> Perhaps the PF wants something that can be *validated*? 

The members of PF are usually happy with statements that can be interpreted
unambiguously, whether or not they are easy to validate with an automated
script. Automation would be ideal, but not required.


> If so, then I see two problems:
>  1) UAs are not *required* to implement the semantics of @hidden via CSS;

True.

>  2) markup validators are not known for throwing errors or warnings for
> incorrect use of CSS;

Also true.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 10 December 2013 03:06:04 UTC