Skip to main content

Search and Top Navigation

#5561 closed bug (wontfix)

Opened April 28, 2010 01:49PM UTC

Closed October 12, 2012 01:06PM UTC

Last modified October 12, 2012 09:10PM UTC

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)
Change History (8)

Changed October 11, 2012 05:41PM UTC by scottgonzalez comment:1

owner: → 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.

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

milestone: TBD1.11.0

Changed October 11, 2012 10:08PM UTC by daveroberts comment:3

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.

Changed October 11, 2012 10:20PM UTC by scottgonzalez comment:4

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.

Changed October 12, 2012 11:06AM UTC by daveroberts comment:5

status: pendingnew

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

Changed October 12, 2012 01:06PM UTC by scottgonzalez comment:6

resolution: → wontfix
status: newclosed

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

Changed October 12, 2012 09:02PM UTC by daveroberts comment:7

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?

Changed October 12, 2012 09:10PM UTC by scottgonzalez comment:8

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.