Opened 13 years ago

Closed 11 years ago

Last modified 11 years ago

#5561 closed bug (wontfix)

DatePicker Truncation in IE6

Reported by: daveroberts Owned by: daveroberts
Priority: minor Milestone: 1.11.0
Component: ui.datepicker Version: 1.8
Keywords: Cc:
Blocked by: Blocking:


I have a large table where the height exceeds my screen height. Inside this table I have cells which contain date picker inputs. In IE6, when the page loads, the last few rows are truncated from the table. It appears they are truncated where the height of the table is being truncated at a height of 100% of the browser window's height. If you comment out the line which turns the inputs into datepickers, the problem never occurs.

Attachments (1) (44.2 KB) - added by daveroberts 13 years ago.
Sample of the Truncation

Download all attachments as: .zip

Change History (9)

Changed 13 years ago by daveroberts

Attachment: added

Sample of the Truncation

comment:1 Changed 11 years ago by Scott González

Owner: set to daveroberts
Status: newpending

My first guess is that this is related to quirks mode. If you're still having problems with the latest version, please provide a reduced test case using jQuery UI 1.9.0 and a doctype that triggers standards mode.

comment:2 Changed 11 years ago by Scott González

Milestone: TBD1.11.0

comment:3 Changed 11 years ago by daveroberts

Status: pendingnew

The example I provided is as small as I can make it as it's required to fill the height of the screen.

comment:4 Changed 11 years ago by Scott González

Status: newpending

How about something that doesn't require a zip. A single HTML file that uses the latest version fo jQuery UI and standards mode. Preferably on jsbin or jsfiddle.

comment:5 Changed 11 years ago by daveroberts

Status: pendingnew

I don't have access to an IE6 system anymore.

comment:6 Changed 11 years ago by Scott González

Resolution: wontfix
Status: newclosed

In that case, I assume this isn't affecting you anymore.

comment:7 Changed 11 years ago by daveroberts

But it may be affecting other users. Is the point of the bug report to satisfy the person who reported it or to fix bugs in the framework?

comment:8 Changed 11 years ago by Scott González

Presumably nobody else has run across this problem (we tend to get a lot of "me too" responses when that's the case). It's been two years since you reported this and there has been absolutely no activity around this. We're dropping IE6 support in a few months and we've already started a complete rewrite of datepicker. So if nobody else is having this problem today, then there's no reason for us to fix it.

Note: See TracTickets for help on using tickets.