Bug 495310

Summary: Cannot drag downloaded images from notification popups to websites in Google Chrome
Product: [Plasma] plasmashell Reporter: Ilya Bizyaev <bizyaev>
Component: NotificationsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: justin, kde, nate
Priority: NOR    
Version First Reported In: 6.2.1   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ilya Bizyaev 2024-10-24 18:56:01 UTC
STEPS TO REPRODUCE
0. Ensure that plasma-browser-integration is installed and working.
1. Open the Lens pop-up on https://images.google.com/
2. Open https://invent.kde.org/-/project/2775/uploads/a4c27c9d5d17dfdc58202eba85a383c1/image.png in Chrome, download it.
2. While the notification is still in its pop-up state, drag the image icon to Lens for search.

OBSERVED RESULT
The image cannot be dropped, which is indicated by the website and the cursor.

EXPECTED RESULT
The image is dropped normally.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20241021
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.3-2-default (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Approaches that do work:
* Dragging the same image from the notification history applet.
* Dragging the same image from Dolphin.
Comment 1 Nate Graham 2024-10-28 04:14:31 UTC
With those steps, this works for me on Firefox (native Wayland) with git master of everything KDE, Qt 6.7.2.

Is Chrome in native Wayland more, or XWayland mode?
Comment 2 Ilya Bizyaev 2024-10-28 12:17:24 UTC
Chrome is in native Wayland mode.
Comment 3 Justin Zobel 2025-05-30 00:16:36 UTC
I cannot reproduce this on git master with Chrome from Flathub in Wayland mode. Can you please confirm this is still an issue on a recent Chrome/Plasma version?
Comment 4 Ilya Bizyaev 2025-05-30 17:42:30 UTC
This happened to me again on the first drag-and-drop, but does not seem to happen on consecutive ones. Since I cannot reproduce the issue reliably anymore, I guess this is good enough.