Bug 2058812 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
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 change the file name to "sあcript.uc.js" from "あscript.uc.js", then it works as expected.

Expected results:
Since these are all valid filenames, they should load correctly.
Revision 1 by
on 
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`


Expected results:
Since these are all valid filenames, they should load correctly.
Revision 2 by
on 
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.

Expected results:
Since these are all valid filenames, they should load correctly.
Revision 3 by
on 
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.

Back to Bug 2058812 Comment 0