If the change underneath breaking backward compatibility was made early enough (on what that department thought were sound grounds) to be deeply embedded in the new code, and the broken compatibility was uncovered late enough in usability testing, then its a corporate decision regarding the cost of fixing the problem, including slipping release dates, and the cost of retaining the problem.


I've been accused of being a Marxist, yet while Harpo's my favourite, it's Groucho I'm always quoting. Odd, that.