Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug 1333403 introduced
browser.menus
as a replacement forbrowser.contextMenus
, keepingcontextMenus
as an alias but recommendingmenus
as the preferred form.Chrome, Opera, and Edge only support
contextMenus
at this time. So, I've tried to handle this by:contextMenus
node in the data tomenus
alternative_name
for Chrome, Opera, and Edge, indicating that these APIs are available undercontextMenus
for those browserscontextMenus
for Firefox.I also need to move
menus
to keep things alphabetical. But that makes the diff really hard to read. So I'v made the change in 2 commits:this commit: 73c00b3 is the one that actually changes the data, but doesn't move
menus
, so should be readablethis commit: eb1b584 only moves
menus
, and doesn't change the data at all.