Moving the mouse over search field in Unified Toolbar bar shows default cursor instead of text edit cursor when entering search bar area from the bottom, with macos 12.7.6
Categories
(Thunderbird :: Toolbars and Tabs, defect)
Tracking
(thunderbird_esr153 affected, thunderbird153 affected, thunderbird154 affected, thunderbird155 affected)
People
(Reporter: Tobbi, Assigned: maxe)
References
(Blocks 1 open bug)
Details
(Keywords: ux-consistency)
Attachments
(1 file, 2 obsolete files)
|
420.09 KB,
video/mp4
|
Details |
I just found an interesting bug that's happening on latest nightly as well as latest release. The cursor that gets shown in the central search bar is different depending on where you enter the search bar from. If you enter it from the left, it shows a default text edit cursor. If you enter it from the bottom, it shows a pointer cursor.
Thunderbird version: 155.0a1 (2026-07-23) (64-Bit)
Steps to reproduce:
- Move the cursor to the left of the central search bar showing in the top center of the Thunderbird window.
- Move it inside the search bar.
- Notice how the cursor displayed is
text. - Move the cursor to the bottom of the central search bar.
- Move it inside the search bar.
Actual results:
Default cursor is displayed.
Expected results:
Text cursor is displayed.
| Reporter | ||
Updated•2 months ago
|
| Reporter | ||
Comment 1•2 months ago
|
||
| Reporter | ||
Updated•2 months ago
|
Comment 2•2 months ago
|
||
FInding the regression range will help.
https://docs.google.com/document/d/1d9uoRxuHyzMKVX4HQSWdKh7XrpE_tBNQ2gap5Q-K3bE/edit?tab=t.0
| Reporter | ||
Comment 3•2 months ago
|
||
I can see this in the mozregression log:
2026-07-26T15:44:59.279000: INFO : Narrowed nightly regression window from [2026-06-11, 2026-06-13] (2 days) to [2026-06-11, 2026-06-12] (1 days) (~0 steps left)
Skimming through the pushlog, I can't really identify a failed commit at first glance.
| Reporter | ||
Comment 4•2 months ago
|
||
Seems like I need to bisect on comm-central, not comm-central-l10n. I'm on it.
| Reporter | ||
Comment 5•2 months ago
•
|
||
| Assignee | ||
Comment 6•2 months ago
|
||
Can you please double-check whether 154 and 153 are fine with the exact same profile/settings?
I was not able to find any regression candidate based on your info.
| Reporter | ||
Comment 7•2 months ago
|
||
(In reply to Max Emig [:maxe] from comment #6)
Can you please double-check whether 154 and 153 are fine with the exact same profile/settings?
Thunderbird Beta (154b1) displays the same issue, so does Thunderbird 153 (as I wrote in comment 0).
| Assignee | ||
Comment 8•2 months ago
|
||
(In reply to Tobias (:Tobbi) Markus from comment #7)
(In reply to Max Emig [:maxe] from comment #6)
Can you please double-check whether 154 and 153 are fine with the exact same profile/settings?
Thunderbird Beta (154b1) displays the same issue, so does Thunderbird 153 (as I wrote in comment 0).
Why are you so certain it's a regression then?
Can you name at least one release where it worked? Otherwise I'm going to remove the regression keywords to avoid more wasted time and resources.
It may very well have been wrong since the 90s imo.
| Reporter | ||
Comment 9•2 months ago
•
|
||
Why are you so certain it's a regression then?
From one of the earlier comments, you can see that I'm not the one who set the regression flags.
Can you name at least one release where it worked? Otherwise I'm going to remove the regression keywords to avoid more wasted time and resources.
I'm gonna run mozregression once more, just to be sure.
It may very well have been wrong since the 90s imo.
Doubtful. The first version of Thunderbird was, according to Wikipedia, released in 2003. So, unless your information differs from the one that's publicly available, a release date in the 90's is unlikely.
Updated•2 months ago
|
| Assignee | ||
Comment 10•2 months ago
|
||
From one of the earlier comments, you can see that I'm not the one who set the regression flags.
I am not entirely sure what happened on Matrix, who came up with the idea that this is a regression, I believe it might not be one.
I'm gonna run mozregression once more, just to be sure.
I ran more advanced tooling and was not able to find anything in recent versions. Any kind of regression check requires a version that is unaffected.
Doubtful. The first version of Thunderbird was, according to Wikipedia, released in 2003. So, unless your information differs from the one that's publicly available, a release date in the 90's is unlikely.
See https://de.wikipedia.org/wiki/Netscape_Communicator, we still have some code from that era as well as incorrect logic that just got ported over.
Comment 11•2 months ago
|
||
(In reply to Tobias (:Tobbi) Markus from comment #9)
Why are you so certain it's a regression then?
From one of the earlier comments, you can see that I'm not the one who set the regression flags.
That would be my error - I assumed you implied this was a new issue that didn't previously exist.
| Assignee | ||
Comment 12•2 months ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #11)
(In reply to Tobias (:Tobbi) Markus from comment #9)
Why are you so certain it's a regression then?
From one of the earlier comments, you can see that I'm not the one who set the regression flags.
That would be my error - I assumed you implied this was a new issue that didn't previously exist.
Even if it was, what would we do with a regression window for a minor UI bug? It's not like we would back anything out anyway or approach a fix any differently.
No hard feelings involved on my side, I would suggest to move to classification what code path is involved in doing that rather than manifesting a regression. Might also be Firefox/Gecko somehow.
| Assignee | ||
Comment 13•2 months ago
|
||
Updated•2 months ago
|
| Assignee | ||
Comment 14•2 months ago
|
||
I determined this is not a regression and built a fix.
Try run if anyone wants to pre-test: https://treeherder.mozilla.org/jobs?repo=try-comm-central&revision=824f3fb2344e42f93e66900efd6dd22a896934b1
Comment 15•2 months ago
|
||
FWIW, I can't repro this on release or beta. I get the text edit cursor either way. Win11 Pro 25H2 build 26200.8875.
| Assignee | ||
Comment 16•2 months ago
|
||
(In reply to Ed from comment #15)
FWIW, I can't repro this on release or beta. I get the text edit cursor either way. Win11 Pro 25H2 build 26200.8875.
Yes, it is not always wrong, only sometimes for some reason. Specifying in CSS can't hurt, though.
| Assignee | ||
Comment 17•2 months ago
|
||
What other software did you have running at the same time?
Anything that might be manipulating the cursor? Any other noteworthy settings? Which macOS version are you on?
On my macOS 26 with Thunderbird Daily it seems correct out of the box.
| Reporter | ||
Comment 18•2 months ago
|
||
(In reply to Max Emig [:maxe] from comment #17)
What other software did you have running at the same time?
I have loads of other stuff running in the background, but I don't think any of those would be manipulating the cursor in such a way, especially since the bug only occurs sometimes and only with that one particular text box.
Anything that might be manipulating the cursor?
Nothing that I can find at first glance.
Any other noteworthy settings?
I don't think so.
Which macOS version are you on?
12.7.6 (21H1320)
On my macOS 26 with Thunderbird Daily it seems correct out of the box.
| Assignee | ||
Comment 19•2 months ago
|
||
I have loads of other stuff running in the background
How about you try a reboot without preserving windows and see if it reproduces with nothing else open?
Comment 20•2 months ago
|
||
(In reply to Max Emig [:maxe] from comment #19)
How about you try a reboot without preserving windows and see if it reproduces with nothing else open?
Sound advice.
Doesn't happen for me on mac 26 with 154 beta
Updated•2 months ago
|
| Reporter | ||
Comment 21•2 months ago
|
||
(In reply to Max Emig [:maxe] from comment #19)
I have loads of other stuff running in the background
How about you try a reboot without preserving windows and see if it reproduces with nothing else open?
It still reproduces after a clean restart when just Thunderbird is open.
| Assignee | ||
Comment 22•1 month ago
|
||
Any more clues? If it works for multiple people here and there is no reason to believe it has anything to do with the code, closing it might be the sanest choice.
Comment 23•25 days ago
|
||
Maybe somehow related to the old version of macOS.
Not seen other reports of this. And still can't reproduce.
| Assignee | ||
Comment 24•8 days ago
|
||
Marking as invalid as neither of us could reproduce and most likely out of our control.
Description
•