[One off searches] Right clicking the settings gear button from Awesomebar opens a context menu with "Search in new tab" and "Set as default search engine" options

NEW
Unassigned

Status

()

P5
normal
2 years ago
4 months ago

People

(Reporter: cirdeiliviu, Unassigned, Mentored)

Tracking

51 Branch
Points:
---

Firefox Tracking Flags

(firefox48 unaffected, firefox49 unaffected, firefox50 unaffected, firefox51 affected)

Details

(Whiteboard: [fxsearch])

(Reporter)

Description

2 years ago
[Affected versions]:
Nightly 51 Build ID 	20160822064441
 
[Affected platforms]:
Ubuntu 15.04 x64, Windows 10 x64

[Steps to reproduce]:
1. Open Firefox with a new profile.
2. Type something in the Awesomebar.
3. Right-click on the settings gear button from the Awesomebar.

[Expected result]:
The context menu should not contain "Search in new tab" and "Set as default engine" options. 

[Actual result]:
A context menu containing "Search in new tab" and "Set as default engine" options is opened. Settings button should have different options than one-off searches engines (or no option at all).
(Reporter)

Updated

2 years ago
status-firefox48: --- → unaffected
status-firefox49: --- → unaffected
status-firefox50: --- → unaffected

Updated

2 years ago
Priority: -- → P2
Whiteboard: [fxsearch]
The settings button shouldn't have a context menu.
Mentor: florian

Updated

2 years ago
Duplicate of this bug: 1300649

Updated

2 years ago
Blocks: 1337003
Priority: P2 → P5
No longer blocks: 1337003
Duplicate of this bug: 1363381

Comment 4

4 months ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → INACTIVE

Updated

4 months ago
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: INACTIVE → ---

Updated

4 months ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.