Currently, a content process will try to open font files directly, instead of asking the parent process to do the filesystem access on its behalf. This should be fixed, and it's currently a problem for content process sandboxing on B2G (and, eventually, desktop Linux). It might be possible to work around this, assuming that the set of font file paths can be determined ahead of time somehow (e.g., on B2G, by walking /system/fonts), when/if at least one of the proposed approaches for open() path filtering works well enough to land. But if this can use the IPC framework, that would probably be better.

Sorry for the bugspam; filter on 086f2ac3-ac15-4299-889b-009181af5029.

Sorry for the bugspam; filter on 086f2ac3-ac15-4299-889b-009181af5029.