Inconsistency: contextMenus/Menus

[erosman]

Inconsistency: contextMenus/Menus

Please note the following inconsistencies in chrome.contextMenus and menus

contexts default

• Chrome & Safari default to ['page']
• Firefox defaults to ['all']

contexts inheritance

Generally, child menus inherit parent's contexts.

• Chrome 'action' child menus do not appear to inherit from their parent's contexts

Unicode support

• Chrome used to fully support Unicode in contextMenus title but not for the last 1-2 years
  e.g. displays U S instead of 🇺🇸 in contextMenus title (as well as action.setBadgeText, action.setTitle)

[xeenon]

Safari defaults to ['page'] like Chrome. We also inherit any parent contexts if the submenu item does not specify any contexts. Emoji's should also be fine in Safari.

[xeenon]

Emoji's do work fine in menu items in Safari.

[carlosjeurissen]

Firefox defaults to ['all']

Using ['all'] as default does not really make sense and seems like not a very conscious decision but the result of the implementation. If changing this in Firefox to ['page'] would lead to backwards compatibility issues, a way to address this could be to in mv4 require to explicitly set the context for top level menus.

Chrome 'action' child menus do not appear to inherit from their parent's contexts

This seems like a bug. Created a crbug for this: https://issues.chromium.org/issues/402806174

Chrome used to fully support Unicode in contextMenus title but not for the last 1-2 years
e.g. displays U S instead of 🇺🇸 in contextMenus title (as well as action.setBadgeText, action.setTitle)

Can not reproduce it. What platform/OS are you using? Emojis display fine for me in Chrome v131 and v135 on macOS Sequoia. They do appear as completely blank in devtools in Chromium tho, while working in Chrome Canary. Opened https://issues.chromium.org/issues/403156532 for this.

[erosman]

Using ['all'] as default does not really make sense and seems like not a very conscious decision but the result of the implementation.

Indeed, it appears to be a consequence of another bug fix.

Can not reproduce it. What platform/OS are you using?

Ubuntu 24.04