Open Bug 1575439 Opened 5 years ago Updated 2 years ago

Firefox asks users to open chrome-extension:// links with external applications when GTK_USE_PORTAL is set

Categories

(Core :: Widget: Gtk, defect)

69 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: frederick888, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

  1. Run "GTK_USE_PORTAL=1 firefox-developer-edition" in a KDE Plasma desktop environment under Linux
  2. Open https://jsfiddle.net/01tpr8sd/

Actual results:

Firefox asks users to open the chrome-extension://kmendfapggjehodndflmmgagdbamhnfd/u2f-comms.html link with an application as shown in the screenshot.

Expected results:

Contents of the iframe should have been an internal error page as chrome-extension:// is an unknown protocol.

Could you please provide more details about how to run Run "GTK_USE_PORTAL=1 firefox-developer-edition" in a KDE Plasma desktop environment under Linux in order to reproduce the bug?
Thanks.

Flags: needinfo?(frederick888)

@Hani Yacoub Copy GTK_USE_PORTAL=1 firefox-developer-edition and paste it into Konsole (or any other terminal emulators) then hit enter. If firefox-developer-edition is not in your search path (you can confirm this using which firefox-developer-edition command in terminal), you'll need to use it's full absolute path instead I think. The absolute path varies depending on the distro and package you're using. If you're using Arch Linux, pacman -Ql <package name> should list all the files installed by the package; if you're using a Debian-based distro, dpkg-query -L <package-name> is the equivalent command to use.

FYI, Arch Wiki also has got some details about how this behaviour can be made persistent: https://wiki.archlinux.org/index.php/firefox#KDE/GNOME_integration and it doesn't necessarily apply only to Arch.

Flags: needinfo?(frederick888)

Setting "Core: Widget: Gtk" component for this bug.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

It seems that with XDG Portal enabled, Firefox simply tries to open all URLs with unknown schemes using Portal. For instance, I can reproduce this issue by putting nonsense: foobar in address bar and hitting enter.

I wonder whether this is a limitation of XDG Portal as there doesn't seem to be an API that can tell callers what URI schemes are available in the system.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: