1710286 - Cursor sometimes disappears after inserting an image into message composition

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[a.balapub]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

when composing a new mail and copying an image into it

Actual results:

Cursors frequently disappears and I have to close the mail I'm composing, and open it again from the Draft folder to see the cursor again.
I've noticed this annoying behaviour for years, in many successive versions of Tbird

Expected results:

The cursor should stay visible until the message composing completion

Comment 1

[Thomas D. (:thomas8)]

a.balapub, I'm failing to reproduce this - can you help?

STR

1.) open a sample image in browser, and "Copy image" from context menu
2.) compose new msg
3.) Paste image
4.) Verify if there's blinking cursor

Actual result == Expected result

• cursor is very close to the image which can make it hard to see (especially if image has black borders), but it's there
• navigation keys (e.g. cursor-left), then Enter to insert new line before image, work as expected, and cursor remains visible always

Comment 2

[Thomas D. (:thomas8)]

Attachment: Screencast for STR of comment 1 - cursor always visible after pasting image

Screencast: STR of comment 1 on 78.10.1 (32-bit) - cursor always visible

Comment 3

[Thomas D. (:thomas8)]

(In reply to Thomas D. (:thomas8) from comment #1)

Reporter, can you pls reply to my comment #1?

Comment 4

[a.balapub]

Hello,
Today TBird work fine (cursor stays blinking on screen).
However, as I told in my report, the cursor disappears relatively frequently when composing a message and incorporating an image
So i'll do two things :
1- get a screen recorder to be able to make a video (have currently none)
2- as soon as the bug appears again, I'll record it and send it

Comment 5

[Thomas D. (:thomas8)]

Ok, thanks a.balapub for reporting back. Even if this was reproducable, the chances of getting this fixed would be very slim - probably Editor territory from Mozilla platform.

Currently we cannot reproduce it, so until more information is available, let's close this worksforme.