Closed (fixed)
Project:
Drupal core
Version:
5.x-dev
Component:
Garland theme
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Dec 2006 at 23:56 UTC
Updated:
13 Jan 2007 at 12:16 UTC
Jump to comment: Most recent file
Comments
Comment #1
Steven commentedCan someone test/verify this in IE7? It matters a lot to how we approach the solution.
Comment #2
keith.smith commentedSee attached screen shot from IE7
Comment #3
Steven commentedI'll see what I can do. This problem is explained partially in this blog post btw:
http://acko.net/blog/mouse-handling-and-absolute-positions-in-javascript
Comment #4
jacauc commentedSubscribing to this, and updating the title.
Comment #5
m3avrck commentedThe latest jQuery version, 1.0.4 has support for pageX and pageY across *all* browsers now, IE included.
http://jquery.com/blog/2006/12/12/jquery-104/
This might help the problem, not to mention with so many nice bugfixes it'll be great to see it in core. I haven't played with it yet but throwing that out there as a possible solution.
Comment #6
Steven commentedErrr no. The jQuery pageX fix is just adding a scroll offset to clientX. It does not help at all, as the problem I had (in the blog entry) was relating these mouse coordinates to element positions. Usually this is accomplished by getting an element's absolute position, which turns out to be a difficult problem (as evidenced in this bug).
Quirksmode has a nice case study:
http://www.quirksmode.org/js/findpos.html
Comment #7
anders.fajerson commentedDoes it have to be positioned with js, maybe CSS could be used instead? I did a testpage for a similair usercase a while ago, which used CSS to postion a DIV relative an input field: http://perifer.se/test/datepickerCSS.htm
Comment #8
Steven commentedHere is a patch which implements the suggested approach. The div is now placed before the input rather than on the top level, and positioned relative to it instead of absolute.
Tested in Safari, Opera and Firefox. Needs IE6 and 7 testing.
Comment #9
ChrisKennedy commentedGreat improvement, patch completely fixes the problem in IE6.
Comment #10
heine commentedFixes the problem in IE 7 as well.
Comment #11
Steven commentedCommitted to HEAD, thanks.
Comment #12
(not verified) commented