This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
4.6.15 and 4.6.16 encourages authors to the class attribute on b/i elements. However many examples in the HTML5 specification where these elements are used does specify any classes. Where it is possible, add classes to these elements in the examples (e.g. change <b>Ian</b> to <b class=name>Ian</b>).
Alternatively, remove the encouragement to use classes...
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.
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 #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, lets 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.
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: Accepted Change Description: no spec change Rationale: One of the two <i> examples and one of the three <b> examples use classes. That seems to satisfy the request that some but not all of the examples use classes.