1881146 - text input caret disappears randomly

Status: UNCONFIRMED

(Core :: DOM: Editor, defect)

Description

[quantumphoton007]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0

Steps to reproduce:

• Open a github issue
• Start typing
• Alt-tab to a different window and then switch back to firefox

This is on firefox, wayland on KDE

Actual results:

The caret (blinking vertical line) disappeared. I can reproduce it on bugzilla.mozilla.org too (right on this textbox where I am typing text).

Sometimes, the cursor keeps blinking while I type. That is, when I type fast enough, the cursor is invisible for 2 seconds and then stays visible for two seconds.

Expected results:

The caret should not have disappeared.
When I type text, the caret should stop blinking until I finish typing text.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Editor' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Edgar Chen [:edgar]]

Thanks for reporting this issue. But I can not reproduce this on Ubuntu 22.04 Wayland.
Do you still see this issue in troubleshoot mode or with clean profile?

Comment 3

[quantumphoton007]

I am on archlinux so I'm probably on much newer package versions compared to u22. My hunch is this is specific to nvidia. I have a different amdgpu machine with a similar setup running arch-kde-wayland with the latest packages which does not have this issue (or any firefox rendering issues really).

In troubleshoot mode, nothing works. The web pages do not respond to my mouse inputs at all. I had to switch back to my current configuration to make it work.

I can try a clean profile but this bug is inconsistent. For instance, after I switched back from troubleshoot mode to my current config, I can no longer reproduce it. I might have to keep using firefox for a while before it shows up.

Comment 4

[Andreas Farre [:farre]]

I'm thinking that we should close this bug, and if it starts recurring again for you we'd be happy to re-open or take another bug for it. Would that be ok for you?

Comment 5

[quantumphoton007]

I noticed this again today but I didn't get a chance to switch to troubleshooting mode. Is there any logging that I can get from firefox about GPU and hardware accelerated mouse cursor while firefox is running?

Comment 6

[quantumphoton007]

Also plasma 6 is just about to be released. I'll give that a try

Comment 7

[Andreas Farre [:farre]]

I don't know of any logging unfortunately. Emilio, do you know of anything?

Thanks, and please report back with your findings. It's very helpful when we can't reproduce on our side.

Comment 8

[Emilio Cobos Álvarez [:emilio]]

So, I can repro something similar on Plasma, but not consistently enough to debug it properly.

Sean was working on bug 1860328 which is somewhat related, my guess is that the focus state gets confused...

If you can reproduce somewhat easily, a MOZ_LOG=Widget:5 could be really useful to confirm whether that's the case...

Comment 9

[ValdikSS]

This happens very frequently with Firefox 130 on KDE5, Wayland, HiDPI (200% "scaling")
I guess this is due to HiDPI configuration, as I haven't seen such an issue also on KDE5 Wayland without HiDPI.

Comment 10

[ValdikSS]

Attachment: 2024-10-01 13-28-15.mp4

Here's the example where the caret freezes in the initial click place, as seen on GitHub issues form.

Comment 11

[Dan Dascalescu]

I've been seeing exactly this issue since Firefox 133 (if not earlier), and still see it in 135. Super annoying.

Happens most often in GitHub text areas, but also in Telegram ones (less often). Clicking in the address bar and then back in the text area sometimes shows the cursor again, other times it doesn't.

Much as I tried, I couldn't find a reliable reproduction sequence.

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.8.9-100.fc38.x86_64 (64-bit)
Graphics Platform: Wayland

Comment 12

[ValdikSS]

This issue is gone on Plasma 6 by the way. This seems to be either Qt or Plasma issue.