Change Search Engines doesn't respond to click when a long string is entered in the search bar
Categories
(Firefox :: Search, defect, P5)
Tracking
()
People
(Reporter: Gabi, Unassigned)
References
Details
(Keywords: steps-wanted)
Attachments
(2 files)
Affected versions
Nightly 73.0a1
Fx 72.0b6
Affected platforms
Windows 10x64
macOS 10.15
Ubuntu 14.4
Steps to reproduce:
- Launch Firefox
- Set browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar to 'false' if enabled
- Go to a new tab
- Enter a long string in Web Search bar
- Click on Change Search Engine setting underneath the search engines
Expected result:
about:preferences#search is opened when Change Search engines is clicked
Actual result:
about:preferences#search page is not opened when Change Search Engines setting is clicked after entering a long string in the Search the Web bar.
Note:
See the attached gif for more information
Regression range
Will search for regression asap.
Reporter | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
This WFM on the latest nightly on MacOS 10.14.
Can you still reproduce?
Reporter | ||
Comment 2•4 years ago
|
||
(In reply to Mark Banner (:standard8) from comment #1)
This WFM on the latest nightly on MacOS 10.14.
Can you still reproduce?
Issue still reproducible with Nightly 73.0a1 20191209095039, verified on Windows 10x64.
Comment 3•4 years ago
|
||
Is there anything on the browser console? Possible related errors?
Reporter | ||
Comment 4•4 years ago
|
||
Reporter | ||
Comment 5•4 years ago
|
||
(In reply to Mark Banner (:standard8) from comment #3)
Is there anything on the browser console? Possible related errors?
I've attached the exported console logs.
Comment 6•4 years ago
|
||
Thanks, I don't think the timeouts reported in the logs are significant. The button for opening the prefs should be different still.
I'm really not sure what is going on here nor why I can't reproduce. Marking as P5 and fix-optional as I don't see users hitting this too often.
Comment 7•4 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Comment 8•4 years ago
|
||
Hi,
I don't think this is a regression, the issue is reproducible in all recent versions, I tried to reproduce it even in 62.0a1 (2018-06-04) and the issue is also present there.
Thanks.
Updated•3 years ago
|
Comment 9•3 years ago
|
||
Just to note, this seems to be a similar cause to bug 1601628 - we queue up a bunch of queries, and in doing so they seem to prevent entry to the settings until it has all caught up.
Description
•