Closed Bug 1383524 Opened 7 years ago Closed 3 years ago

[meta] Removing GDI font api use from the content process

Categories

(Core :: Graphics, enhancement, P3)

Product:
Core
Component:
Graphics
Platform:
Unspecified
Windows
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox57 --- wontfix

People

(Reporter: jimm, Unassigned)

References

(Blocks 1 open bug)

Details

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

We were hoping that directwrite would solve this but unfortunately we're seeing a lot of dwrite related font activity that ends up calling gdi. All of this is going to have to move out of the content process. Filling this as a meta for font use that trigger gdi calls, which will touch on a number of code paths.
Depends on: 1383522
Keywords: meta
Depends on: 1382795
Depends on: 1382232
Priority: -- → P3
Whiteboard: [gfx-noted]
Just wondering, what is the actual goal here, and why do we need to do it? Is this really about "Removing font api use from the content process" altogether, or is it specific to GDI font APIs (as seems to be implied by comment 0)?
The goal is to eliminate usage of GDI system calls so that we can improve sandboxing.
OS: Unspecified → Windows
Summary: [meta] Removing font api use from the content process → [meta] Removing GDI font api use from the content process
Alias: win32k-fonts
Depends on: 1696387
Depends on: 1696407
Depends on: 1698946
Depends on: 1698947
Depends on: 1707767
Depends on: 1713973

We've got a mixture if font related issues blocking this bug and the main win32k-lockdown one, so I think it'll be easier to track this if I move the open ones here to block that bug and I'll close this one.

No longer depends on: 1383522, 1696387, 1713973
Alias: win32k-fonts
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.