IE8 and below do not support some of the basic standards that we use for the 2D mapping. The data viewer functionality works fine but selecting the watersheds for scenario runs is horribly slow due to fundamental flaws in those early versions of IE. (note: they barely work but it's so clunky as to be nearly unusable.)
If we do indeed need to support IE7 or IE8 for any of our clients, we have three options in that case:
Instead of highlighting vector planning units in the browser, we just return rasterized png map tiles. This would involve some significant rewriting of the client side code. Pros: It would work seamlessly in pretty much all browsers. Cons: We'd lose the ability to refine the geography. We would be rewriting a perfectly good approach, making a permanent design decision to support an outdated browser that won't be around in a year or two anyway. Time: about 1-2 weeks.
We support IE7/8 in "data viewer" mode only; if you want scenarios, you would have to use another browser.
We find workaround's for IE's vector data handling flaws (not confident that we could even find a solution; Ed, Scott and I have all spent time on this for past projects without any results)
Removing from this milestone - it barely works (VML is super slow) but it's not enough to force a refactor at this point. See email I sent to Scott and Edwin on 11/14/2012 for details.
IE8 and below do not support some of the basic standards that we use for the 2D mapping. The data viewer functionality works fine but selecting the watersheds for scenario runs is horribly slow due to fundamental flaws in those early versions of IE. (note: they barely work but it's so clunky as to be nearly unusable.)
If we do indeed need to support IE7 or IE8 for any of our clients, we have three options in that case: