Summary: | Firefox keeps asking for being set as default browser when GTK_USE_PORTAL=1 is set | ||
---|---|---|---|
Product: | [Plasma] xdg-desktop-portal-kde | Reporter: | Shmerl <shtetldik> |
Component: | general | Assignee: | Jan Grulich <jgrulich> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | bugseforuns, jgrulich, nate |
Priority: | NOR | Keywords: | usability |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
URL: | https://bugzilla.mozilla.org/show_bug.cgi?id=1516290 | ||
Latest Commit: | Version Fixed In: |
Description
Shmerl
2018-12-16 20:23:16 UTC
To clarify the above. Without GTK_USE_PORTAL=1, Firefox remembers "default browser" setting by creating a NoDisplay .desktop file. Even with that file present, it's still asking when GTK_USE_PORTAL=1 is set. I don't think this has something to do with our portal implementation. I think the problem here is that with GTK_USE_PORTAL=1 Firefox probably thinks it's running in sandbox and tries to read the configuration in a different way or on a different place, no idea. I can file a Mozilla bug if you think that's something on the Firefox side. Opened Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1516290 Comment by Jan Horak: https://bugzilla.mozilla.org/show_bug.cgi?id=1516290#c9 > Setting GTK_USER_PORTAL=1 to get KDE native dialog is generally not a good > idea. The GTK_USER_PORTAL variable is used to detect if the app runs as a > flatpak and that means it cannot use the native print dialog and look for > mimetype handlers in Firefox. |