Comment #16 on issue 2304 by js...@chromium.org: Font problem on clean machines. http://code.google.com/p/chromium/issues/detail?id=2304
Rebaselining on a system without a font covering those characters will results in a test failure on a system with a font covering them. There are two ways to resolve these issues: 1. Persuade CSS 2.1 WG to revise the test 2. Change our test shell code to use a 'tailor-made font' (to be added in our tree) . We have to make that font (or get one with a liberal enough license to be included in our tree). I think CSS 2.1 test-suites need to be revised to be 'font-independent'. Those tests do not need to rely on the availability of those glyphs. Using thumbnail images for those characters preserve what Ian wanted (visual inspection) in them while making them more robust. However, we resolve this issue eventually, I think it's bad to leave them untested. So, I've just made a patch to add revised tests (which I hope will be accepted by CSS WG) to pending. -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
