Browser-specific Manifest entry
# support-framework
a
Browser-specific Manifest entry
I want to add
manifest.browser_specific_settings
only to Firefox, and
manifest.developer
only to Firefox and Opera; how do I do so?
l
What's the current behavior if you add those? Are there any keys that need to be removed for certain platform?
Would "manifest.firefox" works in this case? Or can you use author instead of developer?
a
> What's the current behavior if you add those? The app simply appends to the manifest
> Are there any keys that need to be removed for certain platform? They don't "need" to be removed, but considering that the framework aims for simplicity, I'd expect to have such a feature FYI, on non-Firefox the
browser_specific_settings
is given as a warning, as for
developer
, it's given as a warning for Chrome/Edge
> Would "manifest.firefox" works in this case? Let's put it that way:
browser_specific_settings
can receive values
gecko
,
edge
,
safari
according to https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings So, if I specify
gecko
, I'd expect the non-Firefox manifest to not have
browser_specific_settings
Suppose I specify
opera
as well, I'd expect Opera to only have
browser_specific_settings.opera
and Firefox to only have
browser_specific_settings.gecko
The same applies for Safari
> Or can you use author instead of developer? Technically I can, but using
developer
lets me use a homepage URL on Firefox & Opera https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/developer
which will interopt with the package.json's
homepage
property
3 Views