change event.clientY when an element add before that using javascript on mousemove

RESOLVED INVALID

Status

()

Firefox
General
RESOLVED INVALID
9 years ago
9 years ago

People

(Reporter: Rahman Mousavian, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1

There is a tag on page that with onmousemove event of another element that will appear.
When you add something with javascript before these, the property of this event (clientY and clientX) dosen't work correctly. 



Reproducible: Always

Steps to Reproduce:
1.just refresh the page!
2.
3.
Version: unspecified → Trunk
AFAICT this works correctly as documented at MDC:
https://developer.mozilla.org/en/DOM/event.clientY

I think you need to add window.scrollY/X to get what you want.
https://developer.mozilla.org/en/DOM/window.scrollY

-> INVALID
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
Please also note that the Firefox version you're using is old.
It has several known security issues:
http://www.mozilla.org/security/known-vulnerabilities/firefox30.html
I would recommend updating to the latest 3.0.x version ASAP.
(Help->Check For Updates...)
(Reporter)

Comment 3

9 years ago
I test it in firefox 3.0 , 3.5 , ie6, opera and chrome
In the ie and both version of firefox it dosn't work correctly, but in hte opera  and chrome it's fine.
using of window.scrollY/X can make this true in firefox.
But I guess "clientY" must return the vertical position of the element in the page when the event occur.

as this link(https://developer.mozilla.org/en/DOM/event.clientY) said : 

Returns the "vertical coordinate <<within>> the application's client area at which the event occurred".

It just happened to me, and I thought that may help you to make firefox better. ;)
You need to log in before you can comment on or make changes to this bug.