Video controls don't auto-hide when cursor is moved to another monitor
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: matrix.org, Unassigned)
Details
Attachments
(1 file)
|
6.20 MB,
video/webm
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
- Start playing a video in a
<video>element with thecontrolsattribute. - Make full-screen.
- Move cursor to another monitor.
Actual results:
The controls stayed up.
Expected results:
The controls should have gone away. This is the behaviour when the mouse cursor stops moving or the cursor is moved outside of the video window (onto the webpage).
It seems like this is just and edge case where Wayland stops sending cursor events when the cursor moves out of the window. This likely would also work single-monitor with the video at the edge of the webpage but it easier to reproduce with multi-monitor and full-screen. Even if no more input events are sent the controls should likely time out like when the mouse stops moving on top of the video.
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•3 years ago
|
||
Can you create a screencast of the issue?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Collect_information_for_a_bug_report
Thanks.
|
Reporter | |
Comment 3•3 years ago
|
||
Screencast of the problem.
First the working features are demonstrated.
- Moving the cursor off the video to the document hides the controls.
- Letting the cursor rest for a couple sends hides the controls.
Then I demonstrate that moving the cursor off the window leaves the controls visible, even when waiting for a while. Moving the cursor back over the video then waiting does hide the controls.
|
|
||
Comment 4•2 years ago
|
||
Do you still see that?
Thanks.
|
|
Reporter | |
Comment 5•2 years ago
|
||
Yup. Still see it on 113.0.2.
|
||
Comment 6•2 years ago
|
||
(In reply to Kevin Cox [@kevincox:matrix.org] from comment #5)
Yup. Still see it on 113.0.2.
Does the problem also occur when starting Firefox with MOZ_ENABLE_WAYLAND=1 env var?
$ MOZ_ENABLE_WAYLAND=1 firefox
Description
•