Double-click word selection within a message fails inconsistently.
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
People
(Reporter: bsglick, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36
Steps to reproduce:
Compose an email message. Double-click on a word within the message to select the word so that it can be replaced. Just after the second click, accidentally move the mouse cursor slightly.
Actual results:
Instead of the whole word being selected, only part of the word is selected according to where I moved the mouse cursor.
Expected results:
The whole word should have been selected.
This bug is relatively minor, but it's a regression relative to earlier versions of Thunderbird, and it annoys me on a regular basis.
Comment 1•1 month ago
|
||
Would you be able to pinpoint the regressor, using https://mozilla.github.io/mozregression/ ?
Sorry, mozregression looks like a nice tool and I launched it, but I'm not comfortable using it with Thunderbird because I would need to re-configure my email system. I'm not entirely sure how to do that, and I'm concerned about messing up my current Thunderbird installation.
Comment 3•1 month ago
|
||
I don't understand why clicking after moving the mouse and clicking shouldn't alter the alter the word selection.
Also, I can't reproduce this when using a touchpad.
Do you have all imap accounts? And do you have any message filters that move a message to a local folder?
A rapid double-click on a word should select the entire word. That doesn't happen now in Thunderbird if the mouse cursor moves slightly between the first and second click. Instead, the subtle mouse cursor movement results in selection of only part of the word. This problem may be particularly evident with long words. I'm using a mouse, haven't tried with a touchpad.
I don't see a way to add an attachment, but here is a Dropbox link to a brief movie illustrating the issue:
When I double-clicked in MS Word, the whole word was always selected. But when I did the same thing in Thunderbird, I only succeeded in selecting the whole word one time out of four.
It may be a question of a parameter setting. In software other than Thunderbird, if I double-click while moving the mouse cursor substantially between the first and second click, there is no selection, which makes sense. But if I move the mouse cursor only very slightly between the first and second click, the whole word is selected, as it should be.
=====
I have an IMAP account, with no message filters as far as I know.
Updated•1 month ago
|
Comment 5•23 days ago
|
||
QA can you reproduce?
Comment 6•22 days ago
|
||
Hello!
I tried to reproduce this on macOS Sequoia 15.4.7 and I was not able to reproduce it.
I have downloaded TB 151.0, configured an IMAP account, composed a new message
and double-clicked on various words, including the specific word used by the reporter, while slightly move the mouse between the first and second click. I tested this with both a touchpad and a mouse.
After I updated TB to 153.0 and repeat the scenarios, the whole world was correctly selected.
Update Tb to latest 156.0 and repeated the scenarios and everything worked as expected.
I'm no longer seeing the problem (macOS 26.6.2, TB 155.0), so maybe this one can be put to bed. Thanks for looking into it.
Ben
Comment 8•22 days ago
|
||
Thanks for the update
Scratch that—I just ran into the bug again. Interestingly, it was in the context of a longer message. My test message from earlier today was just a couple of lines, and I didn't see the bug. But when I had a longer message, the bug was visible when I double-clicked in words from the 6th line of the message down.
I still see the bug if I repeat the simple test in the movie that I linked to previously. Specifically:
• Compose a new message.
• Type "Is antidisestablishmentarianism a word?"
• Try double-clicking in "antidisestablishmentarianism" while slightly moving the mouse to the left.
If you can't reproduce it that way, maybe it's just a weird glitch with my system.
Description
•