Object
Mandatory No Manifest version 3 or higher Example
"action": {
"default_icon": {
"16": "button/geo-16.png",
"32": "button/geo-32.png"
},
"default_title": "Whereami?",
"default_popup": "popup/geo.html",
"theme_icons": [{
"light": "icons/geo-16-light.png",
"dark": "icons/geo-16.png",
"size": 16
}, {
"light": "icons/geo-32-light.png",
"dark": "icons/geo-32.png",
"size": 32
}]
}
An action is a button that your extension adds to the browser's toolbar. The button has an icon, and may optionally have a popup whose content is specified using HTML, CSS, and JavaScript.
This key replaces browser_action
in Manifest V3 extensions.
You must specify this key to include a browser toolbar button in your extension. When specified, you can manipulate the button programmatically using the action
API.
If you supply a popup, then the popup is opened when the user clicks the button, and your JavaScript running in the popup can handle the user's interaction with it. If you don't supply a popup, then a click event is dispatched to your extension's background scripts when the user clicks the button.
SyntaxThe action
key is an object that may have any of these properties, all optional:
browser_style
Boolean
Optional, defaulting to false
.
Do not set browser_style
to true: its support in Manifest V3 was removed in Firefox 118. See Manifest V3 migration for browser_style
.
default_area
String
Defines the part of the browser in which the button is initially placed. This is a string that may take one of four values:
This property is only supported in Firefox.
This property is optional, and defaults to "menupanel".
Firefox remembers the default_area
setting for an extension, even if that extension is uninstalled and subsequently reinstalled. To force the browser to acknowledge a new value for default_area
, the id of the extension must be changed.
An extension can't change the location of the button after it has been installed, but the user may be able to move the button using the browser's built-in UI customization mechanism.
default_icon
Object
or String
Use this to specify one or more icons for the action. The icon is shown in the browser toolbar by default.
Icons are specified as URLs relative to the manifest.json file itself.
You can specify a single icon file by supplying a string here:
"default_icon": "path/to/geo.svg"
To specify multiple icons in different sizes, specify an object here. The name of each property is the icon's height in pixels, and must be convertible to an integer. The value is the URL. For example:
"default_icon": {
"16": "path/to/geo-16.png",
"32": "path/to/geo-32.png"
}
You cannot specify multiple icons of the same sizes.
See Choosing icon sizes for more guidance on this.
default_popup
String
The path to an HTML file containing the specification of the popup.
The HTML file may include CSS and JavaScript files using <link>
and <script>
elements, just like a normal web page. However, <script>
must have src
attribute to load a file. Don't use <script>
with embedded code, because you'll get a confusing Content Violation Policy error.
Unlike a normal web page, JavaScript running in the popup can access all the WebExtension APIs (subject, of course, to the extension having the appropriate permissions).
This is a localizable property.
default_title
String
Tooltip for the button, displayed when the user moves their mouse over it. If the button is added to the browser's menu panel, this is also shown under the app icon.
This is a localizable property.
theme_icons
Array
This property enables you to specify different icons for themes depending on whether Firefox detects that the theme uses dark or light text.
If this property is present, it's an array containing at least one ThemeIcons
object. A ThemeIcons
object contains three mandatory properties:
"dark"
"light"
"size"
Icons are specified as URLs relative to the manifest.json file.
You should supply 16x16 and 32x32 (for retina display) ThemeIcons
.
The action's icon may need to be displayed in different sizes in different contexts:
If the browser can't find an icon of the right size in a given situation, it will pick the best match and scale it. Scaling may make the icon appear blurry, so it's important to choose icon sizes carefully.
There are two main approaches to this. You can supply a single icon as an SVG file, and it will be scaled correctly:
"default_icon": "path/to/geo.svg"
Alternatively, you can supply several icons in different sizes, and the browser will pick the best match.
In Firefox:
window.devicePixelRatio
.window.devicePixelRatio
.So you can specify icons that match exactly, on both normal and Retina displays, by supplying three icon files, and specifying them like this:
"default_icon": {
"16": "path/to/geo-16.png",
"32": "path/to/geo-32.png",
"64": "path/to/geo-64.png"
}
If Firefox can't find an exact match for the size it wants, then it will pick the smallest icon specified that's bigger than the ideal size. If all icons are smaller than the ideal size, it will pick the biggest icon specified.
Example"action": {
"default_icon": {
"16": "button/geo-16.png",
"32": "button/geo-32.png"
}
}
An action with just an icon, specified in 2 sizes. The extension's background scripts can receive click events when the user clicks the icon using code like this:
browser.action.onClicked.addListener(handleClick);
"action": {
"default_icon": {
"16": "button/geo-16.png",
"32": "button/geo-32.png"
},
"default_title": "Whereami?",
"default_popup": "popup/geo.html"
}
An action with an icon, a title, and a popup. The popup is shown when the user clicks the button.
Browser compatibilityRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4