Skip to content

Commit db73f0e

Browse files
committed
[css2] New data for issue 95
--HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402385
1 parent 5660f28 commit db73f0e

1 file changed

Lines changed: 18 additions & 0 deletions

File tree

css2/issues/issues-3

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2188,6 +2188,24 @@ following paragraph now in the spec:
21882188
glyph measurement if possible, but may fall back on a default of 0.5em
21892189
if the first available font does not contain suitable information.
21902190

2191+
Ian responded to the second of Bert's ideas above with:
2192+
2193+
> This would work too. It differs from the alternative proposal in that
2194+
> it uses the 'ex' height of the first font _with an x_, rather than
2195+
> the first available font. Is that what we want?
2196+
2197+
To which Bert replied:
2198+
2199+
That's what I gathered from the minutes:
2200+
http://www.w3.org/2005/10/17-css-irc.html#T22-09-17
2201+
2202+
I think the argument was that, if you use an ex and there is an x in the
2203+
content, you would want the two to match. Plus, UAs already know how to
2204+
search the font list for the font with an x.
2205+
2206+
I think that's reasonable, and it made the algorithm nice and short. But
2207+
I'm open for suggestions.
2208+
21912209
=WG= Discuss.
21922210
------------------------------------------------------------------------
21932211
Issue 96.

0 commit comments

Comments
 (0)