Or perhaps there's a different explanation that you might consider before leaping to conclusions...
Our entire web-based sales process is very dated, and it's being completely re-written, from scratch, over the next few months. We researched this problem with IE and it only started in the recent IE version, without us changing anything on our end for years. So something changed in the way IE handles things, and it's not something we did. Consequently, figuring out the issue and fixing it will be very time-consuming. More importantly, the issue only effects a small number of people with the latest version of IE.
Since we're already going to be re-writing the whole thing shortly, and figuring out the problem will take lots of time and effort that will be thrown away a short while later, it makes zero sense for us to fix the issue right now. Until the re-write is done, the small number of people who run into this issue will need to use to an alternate browser. Once the re-write is completed, lots of annoyances with the current system will go away for everyone, plus this recent issue that's arisen with IE will be gone. At that point, everybody will be much happier.
So please understand that we ARE working on this issue, and it's being addressed as part of the complete re-write.
Hope this helps...
