77043 - HTML special characters and entities not working in HREFs

Status: VERIFIED DUPLICATE of bug 51355

(Core :: DOM: HTML Parser, defect)

Description

[abo]

When a string argument is passed to a javascript function containing HTML
special characters or entitities (like "ÄÖÜäöü" or
"ÄÖÜäöü") javascript will stop execution and
nothing will happen any more. IE can handle such arguments correctly. See the
URL given above for an example.

Comment 1

[abo]

Attachment: Example for a JavaScript function that can't handle HTML special characters or entities

Comment 2

[Jason Johnston]

Special characters are handled just fine by JavaScript.

To show this, try:
<a href="#" onclick="display_message('&Auml;&Ouml;&Uuml; ִײ� &auml;&ouml;&uuml;
הצ�');">

...it works correctly.

What is happening in the testcase is that the special-character entities are
being translated, THEN url-encoded since they are in an href="".

For some reason, though, the single-quotes are being dropped and thus the
function parameter is not being passed as a string, giving a JS error.  This
seems to be a url-encoding issue.

Comment 3

[abo]

What is happening in the testcase is that the special-character entities are 
being translated, THEN url-encoded since they are in an href="".

For some reason, though, the single-quotes are being dropped and thus the 
function parameter is not being passed as a string, giving a JS error.  This 
seems to be a url-encoding issue.

Comment 4

[Phil Schwartau]

Attachment: Testcase with javascript:URL as onClick vs. HREF

Comment 5

[Phil Schwartau]

In NN4.7, both anchors in the above testcase behave the same: you 
get the same alert with foreign characters in each case.

In Mozilla/N6, the onClick example works fine, but the HREF example
errors in the JavaScript Console and produces no alert. 

Reassigning to Parser component - this may simply be a duplicate 
of bug 51355. 

Comment 6

[harishd]

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

Comment 7

[Håkan Waara]

verified dup.