- From: <bugzilla@jessica.w3.org>
- Date: Mon, 09 Jan 2012 20:49:52 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12154
--- Comment #14 from Aryeh Gregor <ayg@aryeh.name> 2012-01-09 20:49:48 UTC ---
(In reply to comment #12)
> And now this spec provision has caused WebKit to change it's UA stylesheet.
>
> Congrats, you have now _reduced_ browser interop!
Some browsers on some platforms with some fonts treat <b><b> visually the same
as <b>, and some don't. This change just made WebKit treat them consistently
the same. It's reduced interop vis-a-vis getComputedStyle(), but not vis-a-vis
rendering.
(In reply to comment #13)
> To be clear, the changes in horizontal widths are _precisely_ the interop
> issues Gecko has run into so far. So it's _exactly_ like kerning as far as I
> can tell.
There are no pages with markup that works out to something like
<b><b>foo</b>bar</b>, where authors expect "foo" and "bar" to be the same
weight? Or, alternatively, where authors expect them to be different weights?
Because if <b> is font-weight: bolder, then both of those expectations are
wrong -- it could be either, depending on font availability, unless you're
using @font-face so that you know exactly what fonts are being used.
> It's just as interoperable or not as anything else between systems with
> different sets of fonts installed, modulo browser bugs (like lack of support
> for weights that are bolder than bold altogether).
Even if the browser supports such fonts, that doesn't mean the font does. In
comment #8, I observe that Arial seems to have multiple weights of bold. The
default Ubuntu font seems not to, per
<https://wiki.ubuntu.com/Ubuntu%20Font%20Family#Fonts>. So if an author does
body { font-family: Arial, sans-serif }
(which has got to be awfully common), then Windows users will get multiple font
weights. Ubuntu users who haven't installed MS fonts will not.
If all browsers supported multiple weights of bold *for all fonts*, then I
agree that it would be just as interoperable as anything else font-related.
But as far as I understand it, that's not going to happen no matter what. Am I
wrong?
--
Configure bugmail: https://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 Monday, 9 January 2012 20:51:55 UTC