- From: Anne van Kesteren <annevk@opera.com>
- Date: Fri, 13 Oct 2006 12:59:07 +0200
- To: "Gorm Haug Eriksen" <gormer@opera.com>, "Subbu Allamaraju" <subbu.allamaraju@gmail.com>
- Cc: "Web APIs WG (public)" <public-webapi@w3.org>
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? > We should discuss further if the specification can be relaxed with > regards to property reading or if we should require that this > specification must be implementable in user side JavaScript. The former doesn't really help interoperability, the latter has never been a goal. > IMO using proprietary Firefox extensions is not really an option. > JavaScript already support 'watch', but I don't think this is widely > implemented (e.g. Opera doesn't support it). ECMAScript 4 will also have support for getters and setters (hopefully compatible with what Firefox and Safari have today) which will most likely make this possible. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Friday, 13 October 2006 10:59:18 UTC