Possible regression in `browserSettings.useDocumentFonts` API in recent browser versions?

My add-on – Enforce Browser Fonts – lets user configure a website to use website’s own fonts or browser fonts.

It does this by manipulating the extension API browserSettings.useDocumentFonts, which is a global configuration, but the add-on turns it into a per-domain configuration.

The working is simple – activate the extension through its icon or keyboard shortcut, and the fonts are switched instantly.

Instantly, until about a month ago. Now, when the extension is activated, it does update browserSettings.useDocumentFonts correctly immediately, but the current tab does not reflect the new setting.

Through trial and error, I found that the current tab adopts the new setting if its reloaded OR if devtools are toggled.

Does anyone know what’s going on here? Any pointers are appreciated.

I’m not aware of an intentional change, but I’ll readily admit I don’t have exhaustive knowledge of all changes :stuck_out_tongue_winking_eye:

I spent a few minutes looking through Firefox bug reports and so far I haven’t found any bugs that seem related to the issue you’ve described. IF possible, I’d strongly reccomend creating a minimal reproduction example and filing a bug report on the WebExtensions product on bugzilla.mozilla.org.

Thank you. Bugzilla looks like a more appropriate place to file my issue at.

I’ve filed a bug – 1972971 - Possible regression in `browserSettings.useDocumentFonts` API in recent browser versions

1 Like

And fixed already! But will have to wait for v142 for the fix.

Thank you @dotproto !

1 Like

Very glad to hear it!