- From: Jim Ley <jim@jibbering.com>
- Date: Fri, 13 Oct 2006 12:05:45 +0100
- To: "Gorm Haug Eriksen" <gormer@opera.com>, "Subbu Allamaraju" <subbu.allamaraju@gmail.com>, "Anne van Kesteren" <annevk@opera.com>
- Cc: "Web APIs WG \(public\)" <public-webapi@w3.org>
"Anne van Kesteren" <annevk@opera.com> > On Fri, 13 Oct 2006 11:31:37 +0200, Gorm Haug Eriksen <gormer@opera.com> > wrote: >> I think Allamarajus issue is valid. Having closely tied browser >> specifications that are not implementable in the browser is questionable. > > What do you mean with this? It's a popular strategy to implement new the new APIs by virtue of using older ones in JS libaries so the scripter only writes to the new API but still has it working in old user agents. I'm not sure if it's particularly important that these shims are conformant to the specification though, as they are internal to the use so interopability is not helped a great deal. I'm sympathetic to both views, it's certainly a very valid and real issue. Cheers, Jim.
Received on Friday, 13 October 2006 11:06:18 UTC