463644 - invalid relaterTarget property in mouseover event, when entering the element from scrollbar

Status: RESOLVED WORKSFORME

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Alexey Androsov]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3

I have <div> with fixed width and height, and overflow: auto.
There are several <p> elements in <div>. <div> has scrollbar.
There is mouseover event listener on each <p>.
When I entering the <div> (and <p>) from the side with scrollbar and trying to access e.relatedTarget property, I get the error (Error: Permission denied to get property XULElement.tagName - ff3)
i think, e.relatedTarget is scrollbar, but have to be the <div> element.

I check it in Win, Lin and Mac on FF3 and FF2
FF3: exception "Error: Permission denied to get property XULElement..."
FF2: return xul:thumb (win), xul:nativescrollbar (mac) elements

there is no error when entering the element from the side without scrollbar

you can check it in my example. firebug (console.log) required 

Reproducible: Always

Steps to Reproduce:
1. create <div> width scrollbar and several <p> inside
2. add mouseover listener to each p
3. try to access e.relatedTarget property in listener
Actual Results:  
FF3: exception "Error: Permission denied to get property XULElement"
FF2: return xul:thumb (win), xul:nativescrollbar (mac) elements

Expected Results:  
FF3 and FF2: e.relatedTarget have to be <div> element

Comment 1

[Juriy "kangax" Zaytsev]

I can reproduce it on Mac (10.6.2) with FF 3.x, but not 3.5.x

Comment 2

[Simon Charette]

I can reproduce this on Linux (Ubuntu 9.10) with FF 3.5.5

Comment 3

[Simon Charette]

Attachment: Testcase

try overing the red box and mouseout on scrollbars

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

Could you try with FF3.6b?

Comment 5

[Simon Charette]

Confirm fixed in FF3.6B2 on Linux x86_64 and Win 32

Comment 6

[Alexey Androsov]

It seems, that this bug is fixed in fx3.6b3. Test in winxp sp3