Search and Top Navigation
#4083 closed bug (worksforme)
Opened February 07, 2009 08:04AM UTC
Closed April 10, 2009 09:37AM UTC
Last modified January 17, 2010 06:04AM UTC
Datepicker UI Opening at Random / Unexpected Locations
Reported by: | soothsayer | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.8 |
Component: | ui.datepicker | Version: | 1.5.3 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
I have a Datepicker UI linked to a textbox using the following code:
$(document).ready(function(){
txtDOB = $("input[name=txtDOB]");
txtDOB.datepicker();
});
Screenshot of the Textbox: http://arch.kimag.es/share/85588260.jpg
When I click on the textbox, the calendar opens at an unexpected location as seen in this picture
Firefox: http://arch.kimag.es/share/34288230.jpg
I really can't figure out why this is happening. It works perfectly if the textbox is placed in the top regions of the page.
The Actual Problem in a practical situation is here: http://arch.kimag.es/share/66324568.jpg
To avoid the chances of this being a CSS error, I made an absolute vanilla page with no css files. No divs/floats/positioning or any styling.
Just imported jquery.js and ui core.js and it still happens.
I'm attaching along the html file which I created to test if this bug is real. Turns out to be true & cross-browser as well.
Here is a screenshot:
http://img132.imageshack.us/img132/1628/48364612zr7.jpg
Please verify by checking test.html in the attached zip file after extracting:
http://www.quickfilepost.com/download.do?get=f54ecac485c6cb3ab23d0d8e82bd6699
Let me know what your experience is because with this happening, I can never use this component which is critical.
Attachments (2)
Change History (3)
Changed February 12, 2009 11:42PM UTC by comment:1
milestone: | TBD → 1.6 |
---|---|
priority: | critical → major |
Changed March 08, 2009 02:41PM UTC by comment:2
milestone: | 1.7 → 1.8 |
---|
Changed April 10, 2009 09:37AM UTC by comment:3
resolution: | → worksforme |
---|---|
status: | new → closed |
Cannot duplicate with supplied version, 1.5.3, nor latest. Believe to have been fixed in r1820.