255152 - JavaScript command with Special Characters out of Flash-Movie fails

Status: RESOLVED EXPIRED

(Core Graveyard :: Plug-ins, defect)

Description

[Daniel Slamanig]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: Mozilla 1.72, Firefox 0.9.3

Flash-Movie is created with Swishmax. Bug already checked with Swishmax-
Developers, see http://www.swishzone.com/forums/index.php?showtopic=11328
for details.

If a JavaScript command f.e. javascript("window.status = 'this is the 
message'"); uses special Characters (f.e. German "ä" javascript("window.status 
= 'Das ist für die Gäste'");
Mozilla and Firefox do not process the Script, when it comes from a flash-movie 
and contains Special Characters like "ä". If it has no Special Characters, 
everything works fine. 

If I use the same JavaScript directly in the HTML-File (f.e. in the body tag as 
onload-action), everything is fine also in Mozilla and Firefox.

Other Browsers, that have this problem: Netscape 7 (I'm reporting it there). 
Opera shows the script false like %E4 for "ä".

Swishmax-Developers confirm this to be a bug in Mozilla and Firefox, or perhaps 
in the Flashplayer. Please check this. Bug is also reported to Macromedia.

Reproducible: Always
Steps to Reproduce:
1.Roll over a button in a Flashmovie with JavaScript rollover effect like 
Statusbar or alert
2.If Parameter contains a Special Character, the Script is not performed.
3.Exactly same Script in HTML works fine.

Actual Results:  
nothing

Expected Results:  
Display text in the statusbar or in a JavaScript-alert-Dialog.

Bug prevents Flash-processes to work out.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Sounds like the old "plugin API doesn't allow specifying character encodings"
problem...  Mozilla expects strings coming across that API to be  UTF8; it
sounds like the plugin does something different...

Comment 2

[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 3

[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.