W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2013

[Bug 23532] Dealing with undefined

From: <bugzilla@jessica.w3.org>
Date: Thu, 24 Oct 2013 00:45:06 +0000
To: public-script-coord@w3.org
Message-ID: <bug-23532-3890-3bHLp7N6A7@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23532

--- Comment #28 from Allen Wirfs-Brock <allen@wirfs-brock.com> ---
(In reply to Boris Zbarsky from comment #27)
...
> 
> (In reply to Jonas Sicking from comment #26)
> > And then slowly try to migrate old APIs to the new convention.
> 
> In the long run that gives us a mix of APIs using the two conventions, I
> would expect...  Happy to see someone prove me wrong.

No you're right.  But mixed conventions is already the reality for web
developers who work a platform that includes the DOM APIs, the built-in JS
APIs, and third party libraries that typically for the JS conventions. 

It will be better if new DOM APIs to follow the JS conventions, like everybody
else.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 24 October 2013 00:45:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:18 UTC