[contextMenus] create or update contextMenus in a single call

[hanguokai]

The Problem

Current situation, contextMenus.create() or contextMenus.update() needs to specify an ID parameter. If the contextMenus with the ID already exist for create() or doesn't exist for update(), the method will fail (no effect).

Note: there is no contextMenus.get() method. So to ensure that the create or update is executed successfully, developers need to do in this way:

contextMenus.remove/removeAll(() => contextMenus.create());

The Solution

I suggest improving this API to support create or update in a single call. For example, add an override option in createProperties and updateProperties object, or add a new method contextMenus.createOrUpdate().

[oliverdunk]

I think in some situations (Chrome at least) this results in a chrome.runtime.lastError which is impossible to avoid. Usually you can check that property to hide the error from the console but I haven't been able to get that to play nicely with the promises in MV3.

[hanguokai]

I think in some situations (Chrome at least) this results in a chrome.runtime.lastError which is impossible to avoid. Usually you can check that property to hide the error from the console

Note that:

1. if you never change your context menu, you can just ignore the runtime error.
2. if you want to update your context menu, you can't ignore the runtime error. For example, update title from 'menu-title-1' to 'menu-title-2'. In this case, you need to catch the error and remove the menu then create it.

Current contextMenus api is not consistent with other extension apis. For example, alarms.create() and notifications.create() allow override(update) current alarm/notification if alarm name or notificationId is already exist.

If browser vendors don't want to create new api, I suggest change current behavior of contextMenus.create() and contextMenus.update(), don't throw runtime error, instead, if no menu then create it, if have existing menu then update it.

[hanguokai]

Another problem of contextMenus api is that you can't control a single menu order. If you care about the menus order, you have to removeAll() first then create all menus when you update them.