2058812 - Services.scriptloader.loadSubScript() fails to load with Error if the file name begins with a non-Latin character.

Status: NEW

(Core :: XPConnect, defect)

Description

[Alice0775 White]

Steps to reproduce:
Create a file "あscript.uc.js" in the chrome://userchrome/content/ folder which is specified with chrome.manifest.
Try to load the script using Services.scriptloader.loadSubScript method.

Actual results:
Error opening input stream (invalid filename?): chrome://userchrome/content/%E3%81%82script.uc.js

Interestingly, if a non-Latin character appears anywhere other than the beginning of the filename (i.e., "sあcript.uc.js"), the program runs without any problems.
And in the case of file: protocol (although security.allow_unsafe_subscript_loads must be set to true for the nightly build), both work.

Expected results:
Since these are all valid filenames, they should load correctly.

Comment 1

[BugBot [:suhaib / :marco]]

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

For more information, please visit BugBot documentation.

Comment 2

[Tom Schuster]

Is this really a regression from that change? Because that really didn't change how we parse URLs. And I would have expected the error to be Trying to load untrusted URI instead. What happens when you set the preference security.allow_unsafe_subscript_loads to true?

Comment 3

[Alice0775 White]

(In reply to Tom Schuster from comment #2)

Is this really a regression from that change? Because that really didn't change how we parse URLs. And I would have expected the error to be Trying to load untrusted URI instead. What happens when you set the preference security.allow_unsafe_subscript_loads to true?

The issue is reproduced even if set security.allow_unsafe_subscript_loads = true.
And also on Firefox91...

In other words, this problem has existed for some time.

Comment 4

[Tom Schuster]

Thank you for checking!