Bug 490001

Summary: After drag-and-drop, chromium-based browser is not focused when opening an external link
Product: [Plasma] kwin Reporter: Patrick Silva <bugseforuns>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal    
Priority: NOR    
Version First Reported In: 6.1.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
URL: https://issues.chromium.org/issues/354101895
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: requested output

Description Patrick Silva 2024-07-10 03:53:55 UTC 
STEPS TO REPRODUCE
1. use Wayland
2. run a chromium-based browser natively on Wayland and make sure it is your default browser (I have tested Chromium and Vivaldi on my system)
3. open a link from "About Dolphin" dialog - the browser comes to foreground, as expected
4. drag a .jpg file from Dolphin and drop it in your browser
5. open a link from "About Dolphin" dialog again

OBSERVED RESULT
after the last step, the browser unexpectedly does not come to foreground

EXPECTED RESULT
the browser should always be focused when opening an external link

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.8.0
Graphics Platform: Wayland
Comment 1 Patrick Silva 2024-07-10 04:00:52 UTC 
Can reproduce more consistently with links from Thunderbird running natively on Wayland:

1. use Wayland
2. run a chromium-based browser natively on Wayland and make sure it is your default browser (I have tested Chromium and Vivaldi on my system)
3. open a link from Thunderbird running natively on Wayland - the browser comes to foreground, as expected
4. drag a .jpg file from Dolphin and drop it in your browser
5. open a link from Thunderbird again
Comment 2 Vlad Zahorodnii 2024-07-17 13:55:48 UTC 
Can you run chromium with WAYLAND_DEBUG=1 and post the output here please?
Comment 3 Patrick Silva 2024-07-17 14:06:27 UTC 
Created attachment 171741 [details]
requested output
Comment 4 Vlad Zahorodnii 2024-07-19 11:55:04 UTC 
It looks like xdg activation is not being used for some reason. Please report this issue to firefox developers.
Comment 5 Patrick Silva 2024-07-19 14:22:25 UTC 
(In reply to Vlad Zahorodnii from comment #4)
> It looks like xdg activation is not being used for some reason. Please
> report this issue to firefox developers.

You meant "Please report this issue to chromium developers", right? Firefox is not affected. :)

Reported:
https://issues.chromium.org/issues/354101895