[Wayland] Last keystroke sometimes not reflected immediately in text area until another page update is triggered
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: michel, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Run Firefox in GNOME Wayland session with native Wayland backend (via MOZ_ENABLE_WAYLAND=1 environment variable), and WebRender enabled via gfx.webrender.all & gfx.webrender.compositor. widget.wayland_vsync.enabled is also enabled.
Enter text in any text area such as this one.
Actual results:
Sometimes (relatively rarely, every few minutes maybe?), the last keystroke isn't immediately reflected in a text area: the last character written doesn't appear, the last character deleted remains visible, or the cursor doesn't move according to the last cursor key pressed.
However, if the page contents are then updated again — be it in response to another keystroke, or for another reason — the previously invisible change becomes visible correctly.
(One possible explanation could be that the GL drawing commands aren't properly flushed before the wl_surface_commit request is flushed to the Wayland server.)
Expected results:
Every keystroke should be reflected immediately.
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
It may be related to Bug 1615098 if you're using Fedora 32 or new mutter.
btw do you see that also with non-accelerated backend or is that really webrender only?
Thanks.
|
Reporter | |
Comment 3•5 years ago
|
||
(In reply to Martin Stránský [:stransky] from comment #2)
It may be related to Bug 1615098
It's not clear to me what exactly that's about TBH. :) While I have experienced some of the symptoms described there, this report isn't about those. Also note that the problem described here doesn't happen only in fullscreen/maximixed state.
if you're using Fedora 32 or new mutter.
Currently mutter 3.36 on Debian, but I think it already happened with 3.34.
btw do you see that also with non-accelerated backend or is that really webrender only?
I've disabled WebRender for now, and haven't noticed it yet. But maybe I'm just getting lucky... I'll let you know if it happens again.
|
|
Reporter | |
Comment 4•5 years ago
|
||
Didn't seem to happen without WebRender.
It just happened with gfx.webrender.all but without gfx.webrender.compositor.
|
||
Comment 5•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)
|
|
Reporter | |
Comment 7•4 years ago
|
||
(In reply to Robert Mader [:rmader] from comment #6)
Michel, do you still see this?
No, haven't noticed it lately (no idea when it stopped happening). Still using the same Firefox configuration as in the bug description. Feel free to close this, thanks for getting back to me.
|
||
Comment 8•4 years ago
|
||
Thanks, closing then :)
Description
•