Closed
Bug 1741889
Opened 3 years ago
Closed 3 years ago
Specifying a URL port number leads to hostname being interpreted as a protocol
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1618094
People
(Reporter: wshaos, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0
Steps to reproduce:
With the flatpak version of Firefox, type an address that includes a port number into the address bar, for example localhost:8888
.
Actual results:
The "Choose an application" dialog appears looking for an application that can open "localhost" links.
Expected results:
Firefox should have defaulted to http://localhost:8888
for the address and opened the page served by a web server I have running locally.
Other notes:
- If I type out,
http://localhost:8888
then the page loads normally. - If I type "loc", Firefox will suggest previously loaded pages like
localhost:8888
. If I then select that as is, it will open the page by insertinghttp://
in front. However, if I edit it tolocalhost:8889
, it will not insert thehttp://
and will result in the "Choose an application" dialog (even if defaultinghttp://
were not generally desired, it is a bad user experience not to fill in thehttp://
here when autocompleting a previously opened http url). - If I use the non-flatpak version of Firefox,
localhost:8888
opens the page without thehttp://
just fine. - This problem also affects sites other than localhost. That is just the most common case for me. Typing in
www.google.com:443
also results in the "Choose an application" dialog when using the flatpak but opens the page normally for the non-flatpak version.
Reporter | ||
Updated•3 years ago
|
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Caused by widget.use-xdg-desktop-portal: true
, noticed it after enabling portals on non-flatpaked firefox, but was too lazy to report.
Updated•3 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•3 years ago
|
||
Arg, I don't know how #1618094 didn't come up in my searches.
You need to log in
before you can comment on or make changes to this bug.
Description
•