Closed
Bug 1313843
Opened 8 years ago
Closed 8 years ago
One-off searches broken with keyword.enabled=false
Categories
(Firefox :: Search, defect, P3)
Firefox
Search
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dqeswn, Unassigned)
References
Details
(Whiteboard: [fxsearch])
In this case clicking them is no different than pressing enter.
I mentioned this in bug 1309354, but it didn't get any recognition.
See also Bug 1222378, which also presents itself with keyword.enabled=false.
Comment 1•8 years ago
|
||
Seems to only happen for the heuristic result. Maybe related to bug 1179153?
Assignee: nobody → adw
Severity: major → normal
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Priority: -- → P2
Whiteboard: [fxsearch]
Comment 2•8 years ago
|
||
Let's disable one-offs if keyword.enabled=false.
No longer blocks: 1337003
Priority: P2 → P3
Comment 3•8 years ago
|
||
Unassigning myself from non-P1 search bugs for now so I have more time for Photon bugs.
Assignee: adw → nobody
Status: ASSIGNED → NEW
Comment 4•8 years ago
|
||
Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170507100239
This issue is not reproducible anymore - searching by typing in the URL bar and then clicking on any one-off button is now possible when the preference keyword.enabled is set to false (verified on Ubuntu 16.04 and Mac OS X 10.11).
Panos, is this expected in any way? Should the one-offs still be disabled when keyword.enabled=false?
Flags: needinfo?(past)
I can't reproduce it either, neither Bug 1222378. So I guess they were fixed, perhaps in bug 1318070.
Comment 6•8 years ago
|
||
(In reply to Simona B [:simonab ] from comment #4)
> Panos, is this expected in any way? Should the one-offs still be disabled
> when keyword.enabled=false?
It dose sound like this was fixed in another bug, so the workaround I suggested is not necessary. Thanks for checking again!
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(past)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•