Hacker News Reader

If Microsoft (or someone else) built a self-contained "IE6 For Legacy Web Applications" download, that worked like Fluid/Prism (making an individual launcher for each legacy app), allowed a newer IE to live alongside it, and was guaranteed (literally, contractually) to function identically to IE6 proper, most of this problem would go away, I think.

View on HN

"was guaranteed (literally, contractually)"

What benefit does Microsoft get to offset this huge potential liability?

The point of the contractual obligation isn't to assume liability in case they aren't the same, though; it's to force Microsoft (or whoever else) to prove, incontrovertibly, that they are the same, and therefore give the companies no wiggle-room. Without that proof, no company is going to bother either way, no matter how much liability they're spared.

Reply on news.ycombinator.com