303885 - after changing the character-encoding, access to JavaScript functions is blocked

Status: ASSIGNED

(Core :: Security, defect)

Description

[Suomi Hasler, Ayni AG]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

the above application http://ldap.ayni.com is an ldap-administrator, and
presents its output in ISO-8859-1 character-encoding. 

each page from this site has a corresponding meta tag in the header:
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">

as it is a relatively old application, the pages are HTML coded (as opposed to
XHTML). 

When I start working with the application, firefox obstinately turns its
character encoding to UTF-8, which is the standard encoding of the underlying
Linux OS. This makes, that some pages, which eventually I have to edit, are not
correctly displayed/coded. I then change the firefox character-encoding back to
Western ISO 8859-1, using View/Character Encoding. 

After that, I cannot access the Javascript functions any more. Instead, I get in
the Javascript Console: 
Error: uncought exception: Permission denied to get property Window.editFocus

or similar, where Window.editFocus is the Javascript function I wanted to call
via the Edit button in the top-frame. 

Reproducible: Always

Steps to Reproduce:
1. http://ldap.ayni.com
2. enter "ldap" in the LDAP Server field
3. click Submit or type RETURN
4. without userid/password you see only one single entry of the LDAP DIT. click
that entry, and then click the upcoming alert window, in order to make it disappear.
5. in the top-frame select one of the functions ViewChildren, AddChild, Edit,
Delete, which will all open a respective window.
6. View/Character Encoding, change the character-encoding to whatever value
7. again try to incoke one of the above functions ViewChildren, AddChild, Edit,
Delete, they will no longer work.
8. Tools/JavaScript Console, and see what is in there


Actual Results:  
nothing

Expected Results:  
the functions should have been invoked as before the character-encoding change.

behaviour of Linux and Windows version 1.06 of firefox is consistently
reproducing the error.

Comment 1

[shutdown]

This seems to be a wyciwyg:// related problem.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Is this still a problem on trunk?