- From: David Bruant <bruant.d@gmail.com>
- Date: Sat, 16 Mar 2013 14:49:01 +0100
- To: Jonas Sicking <jonas@sicking.cc>, Rick Waldron <waldron.rick@gmail.com>
- CC: Anne van Kesteren <annevk@annevk.nl>, www-dom@w3.org, Yehuda Katz <wycats@gmail.com>
[cc'ing Rick Waldron. For context start of the relevant part of the thread at http://lists.w3.org/Archives/Public/www-dom/2013JanMar/0202.html ] Le 14/03/2013 10:48, David Bruant a écrit : > Le 13/03/2013 16:47, Jonas Sicking a écrit : >> One tricky issue is the exact timing of the call to the .then >> function. It would be great if we could enable the resolver function >> to do things like call .preventDefault on the event, but that might >> require that the .then function is called synchronously which goes >> against [1]. > Maybe people will use that only for a handful of other events and > we'll see a different pattern emerge. > I'd be more in favor of shipping minimalistic futures, see how people > use them and add hooks to DOM events after having a better > understanding of how people use events in combination with Futures, > but not before. I've spent some time looking at jQuery and since they've added Deferred [1] (a promise-family mechanism), I haven't found evidence that they turn an event to a deferred. I'll let jQuery experts Yehuda and Rick tell me if I'm wrong. I also haven't found sign of other libraries doing that either (people knowing about other libraries can jump in here) Assuming I am not mistaken on how jQuery Deferred and events don't interact, I take that as a signal that it might not be something people use and probably even need. David [1] http://api.jquery.com/jQuery.Deferred/
Received on Saturday, 16 March 2013 13:49:37 UTC