Opened 8 years ago

Closed 7 years ago

#15379 closed defect (patchwelcome)

TabContainer: IE7 crashes if width/height larger than viewport (dojo 1.5.2+)

Reported by: Brian Owned by:
Priority: undecided Milestone: tbd
Component: Dijit Version: 1.5
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by bill)

Although working in 1.5.0 and 1.5.1, in 1.5.2, IE 7 will crash if the width/height specified on the TabContainer? div is larger than the browser "window".

Work around is to move the width/height to a surrounding div and set the TabContainer div to width/height of 100%.

NOTE: In the attached example files, I am pointing to a non-existent 1.5.2 version on the Google CDN (they appear to only have up to 1.5.1). To make the examples work, obviously, the dojo/dijit references will need to be pointed to a 1.5.2 build.

ALSO NOTE: The example TabContainer is set to a width/height of 750px x 400px. So, to crash IE7, make sure your IE7 browser window is smaller than 750px x 400px.

Attachments (2)

ie7_tabcontainer_crash_crash.html (2.5 KB) - added by Brian 8 years ago.
TabContainer? width/height Causing IE 7 to Crash - Crash Example
ie7_tabcontainer_crash_working.html (2.3 KB) - added by Brian 8 years ago.
TabContainer? width/height Causing IE 7 to Crash - Work-Around Working Example

Download all attachments as: .zip

Change History (5)

Changed 8 years ago by Brian

TabContainer? width/height Causing IE 7 to Crash - Crash Example

Changed 8 years ago by Brian

TabContainer? width/height Causing IE 7 to Crash - Work-Around Working Example

comment:1 Changed 8 years ago by bill

Description: modified (diff)
Summary: Dojo 1.5.2 Dijit TabContainer Causes IE 7 to CrashTabContainer: IE7 crashes if width/height larger than viewport (dojo 1.5.2+)

That's odd. Indeed, the browser does crash.

comment:2 Changed 7 years ago by haysmark

Curiously IE6 does NOT crash.

comment:3 Changed 7 years ago by bill

Resolution: patchwelcome
Status: newclosed

I'm just not sure how to fix this. Given that we plan to desupport IE7 (and IE6) in the 2.0 release, it may not be worth fixing, but I'll mark it as "patchwelcome" for now, in case someone else can figure out a reasonable fix.

Note: See TracTickets for help on using tickets.