482067 - JS Error: Permission denied to get property XULElement.parentNode

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[bugzilla_mozilla_org]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6

XUL elements like the slider gets exposed to Javascript in events but interaction with the element is restricted, so the browser throws an error when you try to get the sliders parentNode or similar interaction.


Reproducible: Always

Steps to Reproduce:
1. go to the url
2. move your mousecursor into the grey box
3. move your mousecursor out of the grey box to the right so it leaves the box and enters the scrollbar on the right sie of the box
Actual Results:  
firefox throws a JS Error: Permission denied to get property XULElement.parentNode

Expected Results:  
Either firefox should:
1: not expose XUL elements to javascript events at all or
2: allow full interaction with these elements or
3: not throw errors when this interaction is performed but merely return undefined or some such.

Comment 1

[Thor Larholm]

Confirmed.

Exposing the XULElement through relatedTarget might also pose a security risk.

Comment 2

[Thorsten Suckow-Homberg]

See https://bugzilla.mozilla.org/show_bug.cgi?id=504814 for additional testcase.

Comment 3

[Tyler Downer [He/Him]]

Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to the developer's website and download the latest version from there. If you no longer see this issue, please close this bug as RESOLVED, WORKSFORME. If you do see the bug, please post a comment.

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.