- From: <bugzilla@jessica.w3.org>
- Date: Tue, 10 Dec 2013 02:30:59 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19277 --- Comment #27 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> --- (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. Perhaps the PF wants something that can be *validated*? If so, then I see two problems: 1) UAs are not *required* to implement the semantics of @hidden via CSS; 2) markup validators are not known for throwing errors or warnings for incorrect use of CSS; -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 10 December 2013 02:31:00 UTC