- From: Simon Pieters <simonp@opera.com>
- Date: Tue, 10 May 2011 12:04:13 +0200
- To: "Jonas Sicking" <jonas@sicking.cc>
- Cc: "Jacob Rossi" <Jacob.Rossi@microsoft.com>, "www-dom@w3.org" <www-dom@w3.org>, "annevk@opera.com" <annevk@opera.com>
On Tue, 10 May 2011 11:57:22 +0200, Jonas Sicking <jonas@sicking.cc> wrote: >>> The alternative is to force the event to hold some hidden state which >>> indicates if it has been initialized or not. This is worse both from >>> an implementation complexity aspect, as well as removes the ability >>> for pages to check if an event has been initialized (I don't have any >>> use cases for the latter, but it's a nice free bonus) >> >> Some argued for that but DOM Core was then changed to have a flag - >> http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#initialized-flag > > Why? What was the advantage with that approach? I'd rather not head > down a path that'll make us add extra API just to check the > initialized flag if someone comes up with a use case a couple of years > down the road. > > / Jonas <http://www.w3.org/mid/AANLkTimpSgfpxGez4H9WWTVKSM3MKxLKhuYt9VO_uQnW@mail.gmail.com> -- Simon Pieters Opera Software
Received on Tuesday, 10 May 2011 10:04:48 UTC