The specs last a *lot* longer than the current versions of Mozilla, Safari and IE.
There's a place for making sure you have a path from the current implementations to the new standard, but this isn't it. Specifying this behaviour well isn't going to cost anything; some implementations won't be conformant for a little while, but fixing them won't break any existing applications.
Besides which, each of those implementations does a different thing; how do you accurately represent that?
On 2006/04/20, at 9:46 PM, Ian Hickson wrote:
A specification that doesn't accurately represent what implementations do is useless.
-- Mark Nottingham [EMAIL PROTECTED]
