Issue 2304: Font problem on clean machines.
http://code.google.com/p/chromium/issues/detail?id=2304
Comment #6 by [EMAIL PROTECTED]:
Except for a few tests (noted below), all the tests in css2.1 directory
would pass if
I switch the font check order ('Lucida Sans Unicode' before 'Arial Unicode
MS'). They
all use arrows (U+21E6 - U+21EA) supported by both LSU and AUM fonts. Still
I believe
that those arrows make tests fragile (due to the font dependency) without
adding much
value. So, I'd rather talk to the upstream about replacing them with 'ASCII-
equivalents' ('South' arrow is tough :-)).
In the meantime, I can change our code and rebaseline them.
As Nicolar wrote, there are a couple of tests with YinYang symbol:
t0905-c414-flt-fit-01-d-g.html
t0905-c5526-flthw-00-c-g.html
Again, I'd rather get rid of the actual YinYang symbol and add a reference
(or put a
small thumbnail image).
t0905-c5525-fltblck-00-d-ag.html relies on SE arrow (not covered by any
font)
t0805-c5519-brdr-r-01-e.html relies on U+279[8-9]. They're not supported by
any font
on the 'standard' Windows XP.
invalid-UTF-8 expects the glyph for U+FFFD to be present, but again the
standard
windows XP installation does not have it. It's not clear what to do about
this.
Issue attribute updates:
Status: Started
Owner: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] ian.hickson
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
