W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

Re: ACTION-70: Define the scope chain of onFoo events reference issue-1

From: Jim Ley <jim@jibbering.com>
Date: Thu, 16 Mar 2006 20:05:40 -0000
Message-ID: <00bd01c64935$016e0680$44152d82@Snufkin>
To: <public-webapi@w3.org>

"Maciej Stachowiak" <mjs@apple.com>
> This is exactly why it is behavior needs to be specified instead of 
> leaving it undefined and forcing UAs to reverse engineer each other's  de 
> facto behavior.
>
> Thank you for making the point so effectively.

No it doesn't!  you're confusing your need to handle invalid and undefined 
thing in interopable ways, with a need to specify everything _before_ 
anything is implemented, all that does is make specifications infinitely 
long to write and browser vendors to decide to implement half arsed crap in 
the meantime which harms everyone. A small rapid interopable well thought 
out core that can be specified quickly is good.  It prevents <CANVAS/> or 
<V:VML/> appearing in browsers whilst not taking an eternity to author.

Don't confuse specifications with documenting what User Agents do in the 
undefined areas, one is bad, it takes too long and generates infinite Last 
Call comments, the other is something that can be easily and usefully done 
by just a few people.

Chers,

Jim. 
Received on Thursday, 16 March 2006 20:06:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:53 GMT