Using close search-mode will also remove the next alias (if any)
Categories
(Firefox :: Address Bar, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox80 | --- | unaffected |
firefox81 | --- | disabled |
firefox82 | --- | disabled |
firefox83 | --- | verified |
firefox84 | --- | verified |
firefox85 | --- | verified |
People
(Reporter: aflorinescu, Assigned: daisuke)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(3 files)
[Sugested Severity:]
S3
[Environment:]
Ubuntu 20.04 / Windows 10 / Mac 10.13.6
82.0a1 2020-09-15
[Steps:]
- Open Firefox.
- New tab.
- type @google @amazon @ddg @google
- Click x on google search-mode indicator
[Actual Result:]
[ddg search-mode] @google
[Expected Result:]
[amazon search-mode] @ddg @google
[Note:]
Another way to look at it would be to use "@google @google @google @google @google @google", then close the google search mode, which would remove [google search-mode] + next @google, then will translate the next @google alias into [google search-mode], then close again, repeat.
[Regression-Range:]
This seems to be a recent regression, since in Firefox 81 with the update2.* on, I cannot reproduce.
Comment 1•4 years ago
|
||
it sounds like an edge case, should be investigated but it's probably not a show-stopper.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Regression Range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2e2abe718eb21d36932b373f587d11819d0a3674&tochange=6c384e44f2e40426da3fbdcc044ac300206b9850
Maybe regressed by: https://bugzilla.mozilla.org/show_bug.cgi?id=1658964
@Drew, could you take a look over this?
Thanks.
Comment 3•4 years ago
|
||
Yes, that bug is likely, but I agree with Marco that this isn't urgent, and I'm currently working on higher priority update2 bugs. We'll certainly get to this eventually.
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 4•4 years ago
|
||
I checked this one, but could not reproduce this on current m-c.
(Please see the attachment)
Could you please check it, Adrian??
Or, If I am misunderstanding, please let me know.
Thanks.
Reporter | ||
Comment 5•4 years ago
|
||
Interesting, now mac is behaving properly (10.13.6) but it can still can be reproduced on W10 with latest Nightly 83.0a1 20201012152719.
Reporter | ||
Comment 6•4 years ago
|
||
Assignee | ||
Comment 7•4 years ago
|
||
Thank you very much, Adrian!
Yes, and I can reproduce this on ubuntu 18.04 as well.
Assignee | ||
Comment 8•4 years ago
|
||
Updated•4 years ago
|
Comment 10•4 years ago
|
||
bugherder |
Comment 11•4 years ago
|
||
Hi,
I tested this on W10 on FF 83.0a1 20201012152719, reproduced the issue and then tested it on FF 85.0a1 (2020-12-01) (64-bit) and verified that it's fixed. I also checked it on Beta and release.
Regards, Flor.
Description
•