1876729 - Our application handler is not working anymore in Firefox 122.0

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Peter Winters]

Attachment: Schermafbeelding 2024-01-26 135954.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0

Steps to reproduce:

Tried to open a document from our DMS web based application using our OpenIMS Transfer-Agent.
https://doc.openims.com/beheer/installatie/transfer-agent

Actual results:

The protocol handler openimstoolkit:// is not working anymore in Firefox 122.0 even though it is registered as a class in Windows.

Expected results:

The handler should have opened the default app on the PC. This still works in Chrome and Edge, and worked in Firefox 121

Comment 1

[Robert Longson [:longsonr]]

Can you use mozregression to get a regression range?

Comment 2

[Peter Winters]

Attachment: Schermafbeelding 2024-01-26 144401.png

Mozregression crashed, but as you can see from the screenshot, the defect seems to have been introduced in the central build of 2023 -12-07. I'll try a rerun of Mozregression later.

Comment 3

[Tom Schuster]

Most likely another "regression" from bug 1603699.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

:edgul, since you are the author of the regressor, bug 1603699, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 5

[edgul]

If you flip the pref network.url.useDefaultURI to false, does the error still occur?

Comment 6

[Peter Winters]

Flipping network.url.useDefaultURI to False fixes the issue

Comment 7

[Valentin Gosu [:valentin] (he/him)]

Seems to be similar with bug 1876731.
The problem is that according to the URL standard openimstoolkit://http://example.com parses as openimstoolkit://http//example.com. See reference URL parser
bug 1603699 changed things to enforce correct parsing. You can probably avoid this issue by using openimstoolkit: as a prefix, instead of openimstoolkit://

Please let me know if that works.

Comment 8

[Valentin Gosu [:valentin] (he/him)]

(In reply to Peter Winters from comment #0)

The handler should have opened the default app on the PC. This still works in Chrome and Edge, and worked in Firefox 121

Note that Chrome will also be changing this soon: https://bugs.chromium.org/p/chromium/issues/detail?id=1416006

Comment 9

[Peter Winters]

using openimstoolkit: as a prefix, instead of openimstoolkit:// also fixes the problem

Comment 10

[Valentin Gosu [:valentin] (he/him)]

Excellent. Thank you for confirming.