Sort By combobox on the Global search results page is stuck on Relevance, cannot sort by date
Categories
(Thunderbird :: Search, defect, P2)
Tracking
(thunderbird_esr91 unaffected, thunderbird_esr102+ fixed, thunderbird102 affected, thunderbird103 unaffected, thunderbird104 unaffected)
Tracking | Status | |
---|---|---|
thunderbird_esr91 | --- | unaffected |
thunderbird_esr102 | + | fixed |
thunderbird102 | --- | affected |
thunderbird103 | --- | unaffected |
thunderbird104 | --- | unaffected |
People
(Reporter: cpowell, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [Fixed by Bug 1774378])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.53 Safari/537.36
Steps to reproduce:
Entered a search term; received the "Results for:..." page. Clicked on the "Sort by:" combobox/dropdown to change it from Relevance to Date.
[Thunderbird 102 on macOS.]
Actual results:
The combobox does not respond to clicks and is stuck on Relevance.
Expected results:
The combobox should have expanded to let me choose a different sort order.
Comment 1•2 years ago
|
||
Ooops - indeed. Not good! Global search results can no longer be sorted by date, that's a significant loss of functionality. Thanks cpowell for reporting this.
- Alice, could you find the regression range?
- Alex, can you make a plan?
Updated•2 years ago
|
Comment 2•2 years ago
|
||
This works for me with 103.0b2 on Mac. But I do recall reproducing this myself some weeks or months ago, and also thought there was bug or support report.
Comment 3•2 years ago
|
||
Regression window:
https://hg.mozilla.org/comm-central/pushloghtml?fromchange=5a54066d8cfd7f70f64018e5917a6166af97818c&tochange=3f37649134ad7dbf28c6c1dcd440b771de70d9b9
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=fd384d84f3d05d364a74fa6967e416767c8e8759&tochange=352dec7d8c1349d30c72fdefea648d47ad7cab08
Regressed by: Bug 1744009
Fixed window:
https://hg.mozilla.org/comm-central/pushloghtml?fromchange=6e849249b8e15b9b84907714eee9ec2732d607cd&tochange=71882424b430565a3aefd6c54248969b96a54494
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=fa042bbf4c143ee21fb05b382706cf3a2219a4e2&tochange=7982881720ffb2ed2397e39f0e563feb7c883dd8
Bug 1774378 fixed this.
Comment 4•2 years ago
|
||
Thank you so much Alice, outstanding work as usual.
So it seems they're probably gonna uplift this as per Bug 1774378.
Updated•2 years ago
|
Comment 5•2 years ago
|
||
(In reply to Alessandro Castellani [:aleca] from comment #4)
Thank you so much Alice, outstanding work as usual.
So it seems they're probably gonna uplift this as per Bug 1774378.
Yes, the uplift happened in Bug 1774378 Comment 19:
https://hg.mozilla.org/releases/mozilla-esr102/rev/cfe524975e83
status-firefox-esr102: affected → fixed
So the fix will be in TB 102.1.0.
Comment 7•2 years ago
|
||
Verified FIXED by bug 1774378 for TB 102.1.0.
(102.0.3 was still affected)
Updated•2 years ago
|
Updated•2 years ago
|
Description
•