Closed
Bug 271828
Opened 20 years ago
Closed 20 years ago
Bad encoding of link with accented characters
Categories
(Toolkit :: Toolbars and Toolbar Customization, defect)
Toolkit
Toolbars and Toolbar Customization
Tracking
()
VERIFIED
DUPLICATE
of bug 284474
mozilla1.8beta2
People
(Reporter: nicolas, Assigned: jshin1987)
Details
(Keywords: regression)
Attachments
(1 file)
353 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041123 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041123 Camino/0.8+
When clinking in this link <a href="#?string=Hétérogène">Hétérogène</a> in a web
page, I get this in the Location bar: "...?string=H%C3%A9t%C3%A9rog%C3%A8ne",
but in Firefox, I get "...?string=H%E9t%E9rog%E8ne".
This leads to problems eg. in PHP generated pages (when the var in the URL is
passed in the next page, the accented string isn't displayed correctly and can
break the web application).
Reproducible: Always
Steps to Reproduce:
1. Load the attached test case "accents.html"
2. Click on the link "Hétérogène"
3. Read the content of the Location bar
Actual Results:
The end of the text in Location bar reads "...?string=H%C3%A9t%C3%A9rog%C3%A8ne"
Expected Results:
The end of the text in Location bar should read "...?string=H%E9t%E9rog%E8ne"
This is a regression, it works with build 2004112408 (v0.8.2).
Updated•20 years ago
|
Keywords: regression
Target Milestone: --- → Camino0.9
Can you confirm that this is Camino-specific? Can you test on a Firefox trunk
nightly?
The location bar was set to "view#?string=H%E9t%E9rog%E8ne" in build of the
following.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041129
Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.7.5) Gecko/20041107 Firefox/1.0
Works correctly (i.e. "...?string=H%E9t%E9rog%E8ne") with
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20041129
Firefox/0.9.1+
WFM now, too: 2004120108 (v0.8+) (wasn't working on the build I was using this
afternoon, the 20041126 0.8+ NB)
Since the original reporter now WFM and I can also confirm WFM, should this bug
be closed?
I can also confirm that this doesn't seem to be a problem any more (12/2/04
nightly). Closing.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 10•20 years ago
|
||
I'm sorry to say that this is broken again :-(
Mac OS X 10.3.7
NB 2005011808 (v0.8+),
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 11•20 years ago
|
||
Windows version firefox reproduced.
Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.8b) Gecko/20050120 Firefox/1.0+
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 12•20 years ago
|
||
depend or duplicate bug145962 ?
(In reply to comment #12)
> depend or duplicate bug145962 ?
I'd vote neither, since that is an old bug, whereas this is a recent (though
perhaps periodic) regression.
(Bug 145962--and the others mentioned in it--are the same types of problems in
other areas of the code, though.)
Comment 14•20 years ago
|
||
what's the status here? someone said they could repro on win32.
Comment 15•20 years ago
|
||
It happens in firefox too.
Comment 16•20 years ago
|
||
-> xp, marking this toolkit for now since it happens in both FF and Camino
Component: Location Bar & Autocomplete → Toolbars and Toolbar Customization
OS: MacOS X → All
Product: Camino → Toolkit
Hardware: Macintosh → All
Target Milestone: Camino0.9 → mozilla1.8beta2
Comment 17•20 years ago
|
||
Sent this bug to jshin since he's pretty good with encoding bugs afaik
Assignee | ||
Comment 18•20 years ago
|
||
Well, your PHP script should be fixed to handle %-escaped UTF-8 in URL in light
of RFC 3987 (http://www.faqs.org/rfcs/rfc3987.html ). See bug 261929 and bug 284474)
A work-around is to set 'network.standard-url.encode-utf8' to false.
*** This bug has been marked as a duplicate of 284474 ***
Status: NEW → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•