Skip navigation

We recently ran into a timing issue with IE6 where we were programmatically setting ‘selectedIndex’ after onLoad had completed. Essentially, at least IMO, the JS engine was calling the browser’s native methods to render the select index change, BUT – the JS was executing too fast. That is, the C++ was not completing before the next JS line attempted to set the following select’s index, and we encountered some UI lock. I’m not really sure what’s under the hood of IE6, but I imagine there’s some kind of semaphore-like action happening to prevent the UI thread from clobbering itself.Either way, this article saved the day:

YUI: Downshift Your Code

While we didn’t follow this article verbatim, it was very helpful when staring this IE ‘WTF-ery’ between the eyes. 

Advertisements

One Comment

  1. great article. thanks for the tip! IE ‘WTF-ery’ hahaha!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: