Open Bug 1403299 Opened 3 years ago Updated 10 months ago

Support rendering fonts via FreeType on Windows

Categories

(Core :: Graphics: Text, enhancement, P3)

Unspecified
Windows
enhancement

Tracking

()

Tracking Status
firefox57 --- unaffected
firefox58 --- affected

People

(Reporter: jfkthame, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: feature, Whiteboard: [gfx-noted])

I suspect the most straightforward approach to supporting Variation Fonts on Windows will be to include FreeType in the build, and rasterize such fonts via FT instead of DirectWrite. This will allow us to support variations across all versions of Windows.

We probably want to continue using DW for standard (non-variation) fonts, for the best consistency with font rasterization in other applications on the platform, so this will mean having two font back-ends and choosing between them on a per-font basis.
Depends on: 1403300
Fall Creator Update has new APIs (IDWriteFactor6 etc) for axes.
s/IDWriteFactor6/IDWriteFactory6/
Yes, support is beginning to appear in DirectWrite, so we could consider using this; but that would mean that the feature only works on the latest update of Windows, whereas I assume we'll still support Firefox on Win7 for a number of years yet.
Keywords: feature
Priority: -- → P3
Whiteboard: [gfx-noted]
Just adding a note that the Fall Creator update has shipped with support for variable fonts in DirectWrite. Wondering then if the FT option could be 'scoped' only for use in older versions of Windows?
Duplicate of this bug: 1508214

:jfkthame, with the upgrade to windows v1803 is this bug resolved?

Flags: needinfo?(jfkthame)

No, this is something we could consider doing in order to support variable fonts (and maybe other new stuff in due course, like CFF2-format fonts) on older Windows systems where the OS doesn't handle them. So it's a separate issue from what we're running in our CI for testing purposes.

At this point, we haven't made any decision to put resources into this; our current position is that only users on up-to-date Win10 systems get access to the new font features. Whether that's the final word on the matter is basically a question of priorities. (Note that Chrome does implement this, fwiw.)

Flags: needinfo?(jfkthame)

(In reply to Jonathan Kew (:jfkthame) from comment #7)

At this point, we haven't made any decision to put resources into this; our current position is that only users on up-to-date Win10 systems get access to the new font features. Whether that's the final word on the matter is basically a question of priorities. (Note that Chrome does implement this, fwiw.)

How does Chrome implement it?

They include freetype in their windows build, and dynamically choose which rasterizer to use for any given font.

You need to log in before you can comment on or make changes to this bug.