Bug 110540
| Summary: | [chromium] fast/text/international/thai-line-breaks.html needs a new baseline when we move to Precise | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dirk Pranke <dpranke> |
| Component: | Tools / Tests | Assignee: | Dirk Pranke <dpranke> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | phajdan.jr, schenney, tony |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Dirk Pranke
When using the Lucid version of Freetype (via the use_custom_freetype gyp setting), all but two pixel tests pass. The two that fail are:
fast/text/international/thai-line-breaks.html
platform/chromium-linux/fast/text/chromium-linux-fontconfig-renderstyle.html
I haven't tracked down why they're failing yet, but I suspect the fonts themselves might've changed between Lucid and Precise.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Dirk Pranke
I'm adding a TestExpectations suppression for them in bug 110542; it's not worth adding in "lucid"
and "precise" keywords at this point.
Dirk Pranke
Okay, turns out thai-line-breaks appears to fail because of a change in Garuda.ttf.
chromium-linux-fontconfig-renderstyle appears to just be broken on Precise; we're not displaying the nonantiaaliased font nonantialiased. I'll file a separate bug for that and update the subject on this one.