Closed
Bug 161242
Opened 23 years ago
Closed 23 years ago
Need to consider adding support for unescaping non-ascii filenames from URLs
Categories
(Core Graveyard :: File Handling, defect)
Core Graveyard
File Handling
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 163682
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
(Keywords: intl)
This is a followup to bug 76799. The patch there fixes the most common cases,
but the various intl cases will need some care. We will need:
1) A function like nsUnescape that works on Unicode (will likely need a charset)
2) A way to call it from JS.
I sort of wonder how the status bar manages to show the url with the right chars
(including the %-encoded stuff, as far as I can tell....)
![]() |
Assignee | |
Updated•23 years ago
|
![]() |
Assignee | |
Comment 1•23 years ago
|
||
OK. Now that bug 155569 this is "easy"... except the save as code passes around
URL _strings_ instead of URI objects. So we don't have charset information,
since it also does not pass along the document...
Taking; I'll try to work on a fix for this suckiness.
Assignee: law → bzbarsky
Updated•23 years ago
|
QA Contact: sairuh → ruixu
![]() |
Assignee | |
Comment 2•23 years ago
|
||
nhotta fixed this in bug 163682
*** This bug has been marked as a duplicate of 163682 ***
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•