55468 - Error when click the <a href="javascript:alert('Japanese Words')">...

Status: VERIFIED DUPLICATE of bug 51355

(Core :: Internationalization, defect, P3)

Description

[tato]

1. Error when click the <a href="javascript:alert('Japanese Words')">...
' is %27.
2. Error when click the <a href='javascript:alert("Japanese Words")'>...
" is %22.

and...
3. crash when click the <a href='javascript:alert("a")'>...

1.2.3 ware test on 2000100504 Win32
1.2   ware test on 2000100208 Win32/Linux/Mac

Comment 1

[Martin Horwath]

*** Bug 55466 has been marked as a duplicate of this bug. ***

Comment 2

[Jesse Ruderman]

i run into bug 55460 on the page.

Comment 3

[Phil Schwartau]

The given URL is is a nice testcase which begins,

    "Please set the [View]-[Charctor Coding]-Japanese(Shift_JIS)"

You must change this setting in the browser before conducting the test.

 
The characters encountered by the browser are handled by the browser
embedding of the JS Engine, not the JS engine itself. Reassigning to 
Internationalization component for further triage -

Comment 4

[Teruko Kobayashi]

These works fine in 4.75JA Win32.  

Comment 5

[nhottanscp]

I did not see the crash/freeze. I used win32 branch commercial build ID2000101808.
I tried with and without setting charset coding to Shift_JIS.

In fact, the document specifies the charset by META tag but it is wrong
("<!META" is used instead of "<META"). After I corrected the problem no need to
set charset coding manually.

Comment 6

[nhottanscp]

But I can reproduce the error about the alert with Japanese text.
Alert itself works with Japanese text in Shift_JIS (I will attach an example later).
The following also works (I used unicode instead of Shift_JIS).
<a href="javascript:alert('\u3042')">
But usually people does not use unicode to construct their html. So we better
support charset other than ASCII and unicode.

Comment 7

[nhottanscp]

Attachment: HTML file with JS which contains alert() with Shift_JIS text

Comment 8

[nhottanscp]

Adding keyword 4xp.

Comment 9

[nhottanscp]

In the last attachment, I tried to show alert() itself is working with Japanese
text (in Shift_JIS).
But this bug is about <a href="javascript:alert('Japanese Words')"> is not
working with mozilla.

Comment 10

[nhottanscp]

>The characters encountered by the browser are handled by the browser
>embedding of the JS Engine, not the JS engine itself.
Reassign to jst.

Comment 11

[Johnny Stenback (:jst)]

Mozilla's javascript: URL handling is a mess, we escape the non-ASCII characters
in their original charset but we never unescape them - also, the escaped URL has
no charset info in it so even if we did unescape the JS URL before executing it
there's no way to know what charset the URL is encoded as... oh my

Anyway, cleaning this up for mozilla0.9 would be nice.

Comment 12

[Johnny Stenback (:jst)]

This bug has been marked "future" because the original netscape engineer
workingon this is over-burdened. If you feel this is an error, that you or
another known resource will be working on this bug,or if it blocks your work in
some way -- please attach your concern to the bug for reconsideration.

Comment 13

[HJ]

Can't Netscape replace overburned people? This way the work continues and it
will make a lot of Mozilla/Netscape users happy!

Comment 14

[Johnny Stenback (:jst)]

Netscape could probably replace 'overburned' people, but simply replacing
'over-burdened' people wouldn't really solve any problem :-)

Comment 15

[Frank Tang]

It seems when we have non ASCII inside the string, the ' got escaped into %27
but it won't got escaped if it only have ASCII inside.

I think this bug is less important. I agree that we should future this.

Comment 16

[Johnny Stenback (:jst)]

*** Bug 67206 has been marked as a duplicate of this bug. ***

Comment 17

[Henrik Gemal]

Simple testcase:
alert("æ" + String.fromCharCode(13) + "æ" + String.fromCharCode(13));
alert("a" + String.fromCharCode(13) + "a" + String.fromCharCode(13));

Comment 18

[tato]

This bug will cause a trouble in most Japanese pages that is Javascript : It is 
being used. Before, this was recommended more than onclick by the specification 
of Netscape in A tag. Therefore, a problem isn't small.

Now, I am doing such bug workaround.

<script> a = 'japanese words ( non ASCII )' </script>
<a href="javascript:alert(a)">
test
</a>

(^^;;;...However, it isn't recommended to other people.

Comment 19

[Phil Schwartau]

*** Bug 70873 has been marked as a duplicate of this bug. ***

Comment 20

[Jesse Ruderman]

*** This bug has been marked as a duplicate of 51355 ***

Comment 21

[Teruko Kobayashi]

Verified as dup.