Bug 511450

Summary: No support yet for Microsoft Edge flatpak in flatpak-integrator plugin
Product: [Plasma] plasma-browser-integration Reporter: GodEmperorDoge <ziadalexander98>
Component: generalAssignee: Kai Uwe Broulik <kde>
Status: REPORTED ---    
Severity: normal CC: alexis.pollonni
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description GodEmperorDoge 2025-11-01 01:53:12 UTC
SUMMARY
In the flatpak integrator plugin there is a list of flatpak app ids that are mapped to the respective enum for which browser they are based on as well as their native host configuration path. 

https://invent.kde.org/plasma/plasma-browser-integration/-/blob/master/flatpak-integrator/plugin.cpp?ref_type=heads#L140  

I think we need to add [edge](https://flathub.org/en/apps/com.microsoft.Edge) and [edgedev](https://flathub.org/en/apps/com.microsoft.EdgeDev) to this for the flatpak to work. The edge flatpak is not packaged by Microsoft but it is well maintained, and Microsoft has even [recommended it's usage.](https://support.microsoft.com/en-us/topic/xbox-cloud-gaming-in-microsoft-edge-with-steam-deck-43dd011b-0ce8-4810-8302-965be6d53296) 

Is this as simple as adding an entry and specifying the correct path for the native messaging host? If so, I wouldn't mind testing it and making a pull request.

STEPS TO REPRODUCE
1. Try to use the microsoft edge flatpaks with plasma integration 

OBSERVED RESULT
Integration does not work when using edge as the flatpak

EXPECTED RESULT
Integration does work when using the edge flatpak

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.12.48+deb13-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 32.5 GiB of RAM (31.8 GiB usable)
Graphics Processor: llvmpipe


ADDITIONAL INFORMATION
I also mistakenly opened an issue on gitlab. Copied the issue over here.