Closed Bug 881021 Opened 11 years ago Closed 11 years ago

CSS @font-face unicode-range should be used to avoid downloads

Categories

(Core :: Graphics, defect)

21 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 475891

People

(Reporter: chris, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36

Steps to reproduce:

http://chris.improbable.org/experiments/browser/webfonts/universal-noto-sans/all-in-one.html has multiple @font-face declarations which different font-family names and unicode-range declarations

See http://chris.improbable.org/experiments/browser/webfonts/universal-noto-sans/ for other test cases and webpagetest.org sessions


Actual results:

Firefox downloads every font specified in the elements font-family, even if none of the characters in unicode-range  are present.


Expected results:

Firefox should only download fonts which are actually needed to display the page

This is similar to #475891 but in this case the font names are all different.
Component: Untriaged → Graphics
Product: Firefox → Core
Note that `text-transform` also needs to be considered for this. For example, if the HTML contains:

    <p>FOO BAR BAZ</p>

…but this is lowercased through CSS:

    p { text-transform: lowercase; }

…then the font should only be downloaded if the *lowercased* text matches any of the symbols in the given `unicode-range`.
This is adequately covered by bug 475891, I think. Currently, unicode-range is not supported in Gecko. We just need to fix that.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
(In reply to Jonathan Kew (:jfkthame) from comment #2)
> This is adequately covered by bug 475891, I think. Currently, unicode-range
> is not supported in Gecko. We just need to fix that.

That's reasonable - I left it separate as webkit has unicode-range support for display purposes but not the network optimizations.
You need to log in before you can comment on or make changes to this bug.