Bug 76673
| Summary: | Use per-script font settings in Chrome font fallback (last resort) | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jungshik Shin <jshin> |
| Component: | Layout and Rendering | Assignee: | Jungshik Shin <jshin> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap, falken, kenjibaheux |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Jungshik Shin
Currently, Chrome on Windows has a hard-coded list of per-script fallback fonts to use when fonts specified in CSS do not cover a character in question.
Now that we have a richer set of Settings for per-script / per-cSS generic fonts, we should hand down Settings where 'fallback font' selection is done and use that instead of relying on the hard-coded list.
This may require some cross-platform code as well because we need to pass down a pointer to Settings. Then, other ports (Chromium or not) can use that as well.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jungshik Shin
Note that this is in addition to the default font selection based on 'lang' (explicitly specified or inferred from charset, UI language, accept-language etc).
Alexey Proskuryakov
This bug does not have sufficient cross-platform implications to keep tracking it in WebKit bugzilla.