![\"\"](\"https:\/\/blog.mozilla.org\/addons\/files\/2018\/11\/new-aom-600x285.png\")
Changes on this page include:<\/p>\nFollowing the explosion of extension features in Firefox 63, Firefox 64 moved into Beta with a quieter set of capabilities spread across many different areas.<\/p>\n
The most visible change to extensions comes on the user-facing side of Firefox where the add-ons management page (about:addons) received an upgrade.<\/p>\n
Changes on this page include:<\/p>\n
These changes are part of an ongoing redesign of about:addons that will make managing extensions and themes within Firefox simpler and more intuitive. You can expect to see additional changes in 2019.<\/p>\n
As part of our continuing effort to make sure users are aware of when an extension is controlling some aspect of Firefox, the Notification Permissions window now shows when an extension is controlling the browser\u2019s ability to accept or reject web notification requests.<\/p>\n
![\"\"](\"https:\/\/blog.mozilla.org\/addons\/files\/2018\/11\/extension-web-notify-600x554.png\")
<\/p>\n
When an extension is installed, the notification popup is now persistently shown off of the main (hamburger) menu. \u00a0This ensures that the notification is always acknowledged by the user and can\u2019t be accidentally dismissed by switching tabs.<\/p>\n
![\"\"](\"https:\/\/blog.mozilla.org\/addons\/files\/2018\/11\/install-dh.png\")
<\/p>\n
Finally, extensions can now be removed by right-clicking on an extension\u2019s browser action icon and selecting \u201cRemove Extension\u201d from the resulting context menu.<\/p>\n
![\"\"](\"https:\/\/blog.mozilla.org\/addons\/files\/2018\/11\/remove-cm.png\")
<\/p>\n
Firefox 63 saw a large number of improvements for extension context menus and, as promised, there are even more improvements in Firefox 64.<\/p>\n
The biggest change is a new API that can be called from the To use the new API, you must declare the The API is still being documented on MDN at the time of this writing, but the API takes a While waiting for the MDN documentation to go live, I would highly encourage you to check out the terrific blog post<\/a> by Yuki “Piro” Hiroshi<\/a> that covers usage of the new API in great detail.<\/p>\n Other improvements to extension context menus include:<\/p>\n In addition to the extension management in Firefox and the context menu work, many smaller improvements were made throughout the WebExtension API.<\/p>\n A total of 73 features and improvements<\/a> landed as part of Firefox 64. Volunteer contributors were a huge part of this release and a tremendous thank you goes out to our community, including: Oriol Brufau<\/a>, Tomislav Jovanovic<\/a>, Shivam Singhal<\/a>, Tim Nguyen<\/a>, Arshad Kazmi<\/a>, Divyansh Sharma<\/a>, Tom Schuster<\/a>, Tim B<\/a>, Tushar Arora<\/a>, Prathiksha Guruprasad<\/a>. It is the combined efforts of Mozilla and our amazing community that make Firefox a truly unique product. If you are interested in contributing to the WebExtensions ecosystem, please take a look at our wiki<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"contextmenu<\/code> DOM event to set a custom context menu in extension pages. \u00a0This API, browser.menus.overrideContext()<\/code>, allows extensions to hide all default Firefox menu items in favor of providing a custom context menu UI. \u00a0This context menu can consist of multiple top-level menu items from the extension, and may optionally include tab or bookmark context menu items from other extensions.<\/p>\nmenus<\/code> and the brand new menus.overrideContext<\/code> permission. Additionally, to include context menus from other extensions in the tab or bookmarks contexts, you must also declare the tabs<\/code> or bookmarks<\/code> permissions, respectively.<\/p>\ncontextOptions<\/code> object as a parameter, which includes the following values:<\/p>\n\n
showDefaults<\/code>: boolean that indicates whether to include default Firefox menu items in the context menu (defaults to false)<\/li>\ncontext<\/code>: optional parameter that indicates the ContextType<\/code> to override to allow menu items from other extensions in this context menu. Currently, only bookmark<\/code> and tab<\/code> are supported. showDefaults<\/code> cannot be used with this option.<\/li>\nbookmarkId<\/code>: required when context is bookmark<\/code>. Requires bookmarks<\/code> permission.<\/li>\ntabId<\/code>: required when context is tab<\/code>. Requires tabs<\/code> permission.<\/li>\n<\/ul>\n\n
browser.menus.update()<\/code> now allows extensions to update an icon<\/a> without having to delete and recreate the menu item.<\/li>\nmenus.create()<\/code> and menus.update()<\/code> now support a viewTypes<\/a> property. \u00a0This is a list of view types that specifies where the menu item will be shown and can include tab<\/code>, popup<\/code> (pageAction\/browserAction) or sidebar<\/code>. It defaults to any view, including those without a viewType.<\/li>\nmenus.onShown<\/code> and menus.onClicked<\/code> events now include the viewType described above as part of their info object so extensions can determine the type of view where the menu was shown or clicked.<\/li>\nmenus.onClicked<\/code> event also added a button property<\/a> to indicate which mouse button initiated the click (left, middle, right).<\/li>\n<\/ul>\nMinor Improvements in Many Areas<\/h2>\n
Page Actions<\/h3>\n
\n
Tabs<\/h3>\n
\n
Content Scripts<\/h3>\n
\n
Themes<\/h3>\n
\n
Private Browsing<\/h3>\n
\n
tabs.create()<\/code> and windows.create()<\/code> now open the about:privatebrowsing<\/a> page instead of about:newtab.<\/li>\n<\/ul>\nKeyboard Shortcuts<\/h3>\n
\n
Dev Tools<\/h3>\n
\n
Misc \/ Bug Fixes<\/h3>\n
\n
browser.search.search()<\/code> API \u00a0no longer requires user input in order to be called. \u00a0This makes the API much more useful, especially in asynchronous event listeners. \u00a0This feature was also uplifted to Firefox 63.<\/li>\nidentity.launchWebAuthFlow()<\/code> API so that the redirect_uri parameter is no longer mandatory<\/a>. \u00a0This fixes some OAuth services that require the redirect_uri be configured on the service.<\/li>\nport.onMessage<\/code> is now properly fired in content scripts from non-tabs locations<\/a> (sidebar, extension popup views)<\/li>\nThank You<\/h2>\n