Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
Opened by Luca Viggiani (lviggiani) - Monday, 13 November 2017, 11:24 GMT
Last edited by Toolybird (Toolybird) - Friday, 02 June 2023, 07:13 GMT
|
DetailsDescription:
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 |
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.
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.
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.