Comments on: Firefox 3 .pageX / .pageY bug

By: Stephen Stchur

Stephen Stchur — Sun, 11 Jan 2009 20:43:43 +0000

@eric:

Glad it helped you out! FYI, the latest version of the VE MapControl should have the fix for this built in.

By: eric

eric — Sun, 11 Jan 2009 19:15:49 +0000

You just saved me hours worth of work. I spent two hours last ripping through zindexes and float positions trying to figure out why my VE controls were acting this way in FireFox 3 (Chrome and IE7 seem fine, as you noted). Thanks so much. I never would have cleared this otherwise.

By: Gubmimikall

Gubmimikall — Sat, 20 Dec 2008 03:01:59 +0000

The good resource is informative and actual

By: Mike

Mike — Wed, 29 Oct 2008 22:30:40 +0000

Thanks for this.

By: csavage

csavage — Tue, 14 Oct 2008 22:23:24 +0000

I must say, your fix worked perfectly.
Thanks for documenting the issue!

By: sstchur

sstchur — Thu, 09 Oct 2008 20:50:54 +0000

Glad it helped Jon!

By: Jon Hudson

Jon Hudson — Thu, 09 Oct 2008 13:02:49 +0000

I have tried for days to fix this issue for my mapping mashup. Very well done sir! Thank you.

By: Dan Fabulich

Dan Fabulich — Mon, 07 Jul 2008 20:11:11 +0000

Please also follow up with your comments on bug 405632. One Mozilla dev (Smaug) said this on the matter: "IMO http://blog.stchur.com/2008/07/03/firefox-3-pagex-pagey-bug/ describes a feature not a bug. Dispatching an event manually shouldn't be affected by the layout of the page. (Unfortunately pageX/Y and layerX/Y aren't defined in DOM Events specification)"

By: sstchur

sstchur — Mon, 07 Jul 2008 19:34:40 +0000

Ah, thanks Dan!

I see that there has been some chatter on the bug. I've added my comments and voted in hopes of getting it fixed.

By: Dan Fabulich

Dan Fabulich — Mon, 07 Jul 2008 19:24:56 +0000

This bug doesn't say "pageX" in its summary, so a simple search won't turn it up. It will turn up on a search that includes "pageX" in comments. http://tinyurl.com/5zsa23