HTML5 says b and strong have font-weight: bold instead of bolder: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html#fonts-and-colors Some discussion about this can be found at the following HTML5 and Mozilla bugs: http://www.w3.org/Bugs/Public/show_bug.cgi?id=12154 https://bugzilla.mozilla.org/show_bug.cgi?id=589124 Mozilla received reports that some sites displayed incorrectly when Firefox 4 (with DirectWrite enabled on Windows) started actually respecting font-weights higher than 700, because they accidentally nested <b> tags and the text inadvertently became too bold. font-weight: bolder is inherently inconsistent across browsers and so shouldn't be the default style, IMO. Currently all browsers but Opera make b and strong font-weight: bolder, but in practice this is usually not observable because font-weights of 700, 800, and 900 generally get the same fonts assigned to them anyway. So changing to font-weight: bold is likely to increase compatibility, not decrease it. Test-case to demonstrate that the default is font-weight: bolder: data:text/html,<!doctype html> <p style=font-weight:100> <b>Should be bold per HTML5</b> Chrome 11 dev does not display the text bold.
Clearly either we should fix this in WebKit or the spec should change.
Created attachment 99366 [details] Patch
Comment on attachment 99366 [details] Patch Looks sane to me.
Comment on attachment 99366 [details] Patch Clearing flags on attachment: 99366 Committed r103468: <http://trac.webkit.org/changeset/103468>
All reviewed patches have been landed. Closing bug.
For what it's worth, generally if the spec disagrees with _all_ implementations it's the spec that should change, not the implementations. Or so it seems to me. Note that this was explicitly a part of the spec flagged as being buggy, so I'm not sure why the WebKit behavior got changed to follow it...
(In reply to comment #6) > For what it's worth, generally if the spec disagrees with _all_ implementations it's the spec that should change, not the implementations. Or so it seems to me. > > Note that this was explicitly a part of the spec flagged as being buggy, so I'm not sure why the WebKit behavior got changed to follow it... Using font-weight: bolder as the default style of strong/b is problematic at best (e.g. when you nest b's and strong's) inside contenteditable region so I'm glad we changed our behavior.
Spec has been changed to say 'bolder', so this no longer matches the spec.
(In reply to comment #8) > Spec has been changed to say 'bolder', so this no longer matches the spec. The value "bolder" is too troublesome for editing purposes. I don't think we'll change back.