FS#56310 - [mutter] Not sending shift / ctrl key to Chrome and Firefox for drag and drop operations on wayland

Attached to Project: Arch Linux
Opened by Luca Viggiani (lviggiani) - Monday, 13 November 2017, 11:24 GMT
Last edited by Toolybird (Toolybird) - Friday, 02 June 2023, 07:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
In a GNOME on Wayland session, if dropping one or more files into a web browser (both chrome or firefox), the event.shiftKey and event.ctrlKey are always false. It works fine in X11. It was working fine on GNOME 3.24 on Wayland as well.

Additional info:
* package version(s)
mutter 3.26.2-1


Steps to reproduce:
0) On a GNOME on Wayland session:
1) Save and open the attached test.html page in either Chrome or Firefox
2) Open the console (ctrl+shift+i)
3) Drag a file from Nautlis while holding the shift key and look at the console outup
4) You would expect "true" but you get "false"

repeat the seps above on X11: you'll get "true" when holding the shift key down
(text/html)    test.html (0.4 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 02 June 2023, 07:13 GMT
Reason for closing:  Upstream
Additional comments about closing:  If still an issue, please report upstream as requested by PM.
Comment by Luca Viggiani (lviggiani) - Monday, 13 November 2017, 11:34 GMT
This new version of the test page is required for Firefox
(text/html)    test.html (0.5 KiB)
Comment by mattia (nTia89) - Sunday, 27 February 2022, 13:37 GMT
I cannot reproduce the issue. Is it still valid?
Comment by Luca Viggiani (lviggiani) - Monday, 28 February 2022, 08:39 GMT
Yes it's still valid at least on latest Chrome 98.0.4758.102 and Mutter 41.4
Comment by Jan Alexander Steffens (heftig) - Monday, 28 February 2022, 09:02 GMT
Please report this upstream. There's nothing Arch can do about it.

If this is a Firefox issue, I won't be backporting fixes for Wayland to it as long as it's not enabled by default.

If this is a Mutter issue, it might be possible.

Loading...