I would have expected this would get around the issue.Fires when the size of the object is about to change. There is an IE specific onresizeend event, but I couldn't get it to work - I tried setting the event via JS, via VBScript (I had to wash TextMate afterwards it felt so dirty writing VBScript!) and I tried an event specific script tag (as per Microsoft's MSDN page). Safari fires throughout the resize, but doesn't hang. This is why either capping the resize firing or putting the changing content in a fixed height container doesn't cause the error to occur.įirefox handles this issue by firing the resize event once the resize has completed.

Since the window's content height has increased, it triggers a resize event - go to 3.and so we have our infinite loop.

Handler increases the height of the content (not the window, but remember, this is IE).

It will happily add content horizontally, but vertically causes a hang. This bug only occurs when the resize handler (or any functions called from the handler) create new lines of content in the browser. If you remove the limiter, and enable the container, you should find it doesn't hang. If you remove the 'limiter' in IE it should hang the browser.

Upon loading the demo, it's designed not to hang. I've created demo, designed to show you how to prevent the bug from executing and then allowing you to create the scenario that causes the hang.

IE will result in a total hang, that will probably require you to kill the running process. Upon resizing, resizing works fine in all browsers, except IE. You've hooked an onresize event and there's some, supposedly, innocuous code in the handler. $49 - only from this link Details of the Bug

I've published 38 videos for new developers, designers, UX, UI, product owners and anyone who needs to conquer the command line today.

Javascript onresize