- From: Jonas Sicking <jonas@sicking.cc>
- Date: Sun, 26 Jul 2009 20:18:38 -0400
- To: Doug Schepers <schepers@w3.org>
- Cc: Anne van Kesteren <annevk@opera.com>, Jonathan Watt <jwatt@mozilla.com>, Olli Pettay <Olli.Pettay@helsinki.fi>, Jacob Rossi <t-jacobr@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Travis Leithead <travil@microsoft.com>, "www-dom@w3.org" <www-dom@w3.org>, Andrew Sledd <Andrew.Sledd@ikivo.com>, Robin Berjon <robin@berjon.com>, Lee Martineau <lee.martineau@quickoffice.com>
On Sun, Jul 26, 2009 at 7:31 PM, Doug Schepers<schepers@w3.org> wrote: > Hi, Folks- > > Can someone please enlighten me why removing DOMFocusIn, DOMFocusOut, and > DOMActivate from existing implementations seems like a good idea? Boris explains it really well. To me it is really high value to cut "unfortunate" features when ever we can. And to do so as soon as possible before too much content start depending on it. There is always some amount of complexity that we immediately remove by doing this. And long term it is likely that it'll save us more complexity since it makes it easier to add future features. It is especially the future features that I worry about since we have no idea what feature today turns out to be a roadblock for other work tomorrow. For example being able to set document.domain I'm sure seemed like a small change in the past, however it turned out to be a major headache for supporting a namespace-resolver argument to querySelector. / Jonas
Received on Monday, 27 July 2009 00:19:41 UTC