Open Bug 1411898 Opened 7 years ago Updated 2 years ago

Empty Context Menu (WebExtensions)

Categories

(WebExtensions :: Frontend, defect, P5)

56 Branch
defect

Tracking

(firefox57 wontfix)

UNCONFIRMED
Tracking Status
firefox57 --- wontfix

People

(Reporter: pag77, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170926190823

Steps to reproduce:

This is actual for Firefox 56, 57 Beta, 58 Nightly!

1. create main menu-popup:

chrome.contextMenus.create({
	id: 'context_popup',
	type : 'normal',
	title : 'context_popup',
	contexts: ["all"],
	onclick: function(event){ console.log('Click to context_popup!'); }
});

2. create sub-menu:

chrome.contextMenus.create({
	id: 'context_sub_menu',
	type : 'normal',
	title : 'context_sub_menu',
	parentId: 'context_popup',
	contexts: ["selection"],
	onclick: function(event){ console.log('Click to context_sub_menu!'); }
});

3.
select any text in webpage - in context menu: 
'context_popup' > 'context_sub_menu'

but! no select text - in context menu:
'context_popup' > [empty square]



Actual results:

if parent the menu popup 'contexts: ["all"]' and in this popup only the submenu with 'contexts: ["selection"]' (or 'video', 'link', 'image', etc), 
then, if there was no event "selection" (or 'video', 'link', 'image', etc), an empty square is displayed: 'context_popup' > [empty square]



Expected results:

Like as GoogleChrome:
if parent the menu popup 'contexts: ["all"]' and in this popup only the submenu with 'contexts: ["selection"]' (or 'video', 'link', 'image', etc), 
then, if there was no event "selection" (or 'video', 'link', 'image', etc) == 'context_popup' is normal menu-item with onclick-event without popups

otherwise (if showing submenus) the onclick event should not be handled for 'context_popup'
Component: Untriaged → WebExtensions: Untriaged
Product: Firefox → Toolkit
Component: WebExtensions: Untriaged → WebExtensions: Frontend
Priority: -- → P5
Product: Toolkit → WebExtensions
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.