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 mnot@yahoo-inc.comReceived on Friday, 21 April 2006 16:34:48 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT