>It's a cost/benefit issue. Will the costs of fixing this outweigh the benefits to the users? There is a work around. I'm not saying it shouldn't go into an SP, but I'm not saying it should either. I don't have enough statistics on how many people this would affect.

No its not. That's just corporate pro-MS speak. The problem referred to is not some esoteric "one in a million" issue - its a new, acclaimed feature that doesn't work as it should in ordinary and general circumstances. You just cannot defend this and suggest a work around is acceptable.

If I developed a system for a client and they reported a bug to me, what do you think they would say to me if I said to them :-

"It's a cost/benefit issue. Will the costs of fixing this outweigh the benefits to the users?"

They would laugh all the way to their lawyers.