I think that's so that on large pages, when you've scrolled down, the x/y
compensates the scrollbar.
I seem to remember that to get it the same as in IE you had to add 20 or
something.
Cheers,
Richard Bennett
[EMAIL PROTECTED]
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 06, 2001 7:46 PM
Subject: [Dynapi-Help] events.js: mouse event .pageX/Y
> I have a question.
>
> In events.js, setEvent method:
>
> why exactly do we do the following instead of just using e.pageX?
>
> if (is.ns) {
> this.pageX=e.pageX-window.pageXOffset;
> this.pageY=e.pageY-window.pageYOffset;
> }
>
> When I change the above to the following,
>
> if (is.ns) {
> this.pageX=e.pageX;
> this.pageY=e.pageY;
> }
>
> Not only does everything appear to be working (mousemove event coords,
dragging, etc.) correctly, but the pageX/Y now match the same coords as in
IE (it didn't before).
>
> Can anyone answer this?
>
> Is there a reason for it?
>
> Thanks in advance,
>
> --proteanman
>
> _______________________________________________
> Dynapi-Help mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-help
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New! Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
