- From: <bugzilla@jessica.w3.org>
- Date: Fri, 03 May 2013 15:21:38 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21920 Bug ID: 21920 Summary: make note on heading use clearer Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P3 Component: HTML5 spec Assignee: dave.null@w3.org Reporter: faulkner.steve@gmail.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org comment on note at top of http://www.w3.org/html/wg/drafts/html/master/common-idioms.html#sub-head comment from: http://html5doctor.com/howto-subheadings/#comment-34126 It's confusing because it isn't clear what the status is of a spec telling authors “do not do this, but it isn't the case that you must not do it, nor even the case that you should not do it”. If I do do it, so what? Nobody can complain that I'm not meeting the spec's requirements. Or if somebody did wish me to follow commands such as that, they could request that I write “valid HTML which complies with all ‘do not’ commands in the spec” — which as well as being unweidly, also <i>de facto</i> introduces a third level of conformance requirements. If it's really something that authors shouldn't do, then make it a proper conformance requirement. If it's OK for them to do it, don't tell them not to do it. If that makes sense to you and this is something you're interested in fixing, feel free to copy my comment into a bug report, if that helps with the process. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 3 May 2013 15:21:40 UTC