278130 - Named anchor with Korean/Japanese Character does not work

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Gowri Kandasamy]

Named anchor with Korean chaaracter doesn't work.

In the following link doesn't work.
http://docs.hp.com/ko/allproducts.html#bh7800%20%BC%AD%B9%F6 

But if the anchor is all English , then works fine.
http://docs.hp.com/ko/allproducts.html#CDE

I see the same problem in mozilla  1.4 , 1.6 , 1.7 

This works fine in IE .

Comment 1

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20050111
Firefox/1.0+

WFM

(same behaviour IS/Opera/FF)

Comment 2

[Simon Montagu :smontagu]

This may be a dupe, but we also need to check whether named anchors are impacted
by the fix for bug 261929.

Comment 3

[Jungshik Shin]

I can reproduce this on Linux with 1.7. Needs a bit of playing with, though

Yeah, I was also worried about the named anchor after landing the fix for bug
261929.  Once the document is returned from the server, it's under our control
so that we should be able to take care of it... Perhaps, with UTF-8 always used
(IRI), it may be easier than before (of course, it's still a pref. so that we
have to deal with non-IRI cases as well...)

What component does this belong? parser? 

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 6

[Simon Montagu :smontagu]

What is the current status of this? Comment 2 and comment 3 are no longer
relevant...

Comment 7

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20051020
Firefox/1.5 ID:2005102014

It's still WFM

Comment 8

[Jungshik Shin]

WFM regardless of the value of network.standard-url.encode-utf8