Skip to main content

Search and Top Navigation

#6263 closed bug (invalid)

Opened November 04, 2010 02:44PM UTC

Closed November 03, 2012 08:52AM UTC

Datepicker is opened in wrong position in IE6 when body has "position:fixed" in style

Reported by: maxbarbul Owned by: maxbarbul
Priority: minor Milestone: 1.11.0
Component: ui.datepicker Version: 1.8.5
Keywords: ie6 Cc:
Blocked by: Blocking:

In attached example HTML you can see the demo of datepicker from UI site. Only I changed some links and set style="position: fixed" for BODY element (as we use in our app).

In this case datepicker appears in wrong position. Without position:fixed it's OK.

I found place in datepicker code where position:fixed is applied to widget container of datepicker. So I changed the condition to not meet BODY and HTML elements in search of parents (see attached patch).

Attachments (3)
  • datepicker.bug.PNG (5.2 KB) - added by maxbarbul November 04, 2010 04:53PM UTC.

    Screen shot of bug

  • datepicker.example.html (0.8 KB) - added by maxbarbul November 04, 2010 02:46PM UTC.

    This is example where you can see the problem

  • jquery.ui.datepicker.patch.txt (0.4 KB) - added by maxbarbul November 04, 2010 02:46PM UTC.

    This is the patch that fixes problem (for me it's OK)

Change History (3)

Changed October 11, 2012 09:04PM UTC by scottgonzalez comment:1

milestone: TBD1.11.0

Changed October 19, 2012 03:18PM UTC by mikesherov comment:2

owner: → maxbarbul
status: newpending

Hi, and thanks for contributing! We're going to be phasing out IE6 support eventually, but I'd like to know what the use case for putting position: fixed on the body element is?

Changed November 03, 2012 08:52AM UTC by trac-o-bot comment:3

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!