- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Oct 2010 08:14:02 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10735 Peter Winnberg <peter.winnberg@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #4 from Peter Winnberg <peter.winnberg@gmail.com> 2010-10-12 08:14:02 UTC --- (In reply to comment #3) > Checked in as WHATWG revision r5555. > Check-in comment: don't encourage use of 'class' so much > http://html5.org/tools/web-apps-tracker?from=5554&to=5555 (In reply to comment #2) > EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are > satisfied with this response, please change the state of this bug to CLOSED. If > you have additional information and would like the editor to reconsider, please > reopen this bug. If you would like to escalate the issue to the full HTML > Working Group, please add the TrackerRequest keyword to this bug, and suggest > title and text for the tracker issue; or you may create a tracker issue > yourself, if you are able to do so. For more details, see this document: > http://dev.w3.org/html5/decision-policy/decision-policy.html > > Status: Partially Accepted > Change Description: see diff given below > Rationale: Concurred with comment 1 to address problem in comment 0. Ok, let’s try again. I think encouraging authors to use classes on these elements was a good thing because of the obvious problems with using them without classes. And using them in (some of) the examples would help authors to see the benefits of doing this. Trying to weaken the text about the classes in these elements in order to avoid making changes to the examples is not a solution to this, quite the opposite actually. That said this does not have to mean that all examples that use b/i elements have to use it. -- Configure bugmail: http://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 Tuesday, 12 October 2010 08:14:04 UTC