- From: Rich Tibbett <richt@opera.com>
- Date: Wed, 29 Sep 2010 00:58:55 +0200
- To: public-device-apis@w3.org, Frederick.Hirsch@nokia.com
On Tue, 28 Sep 2010 21:48:25 +0200, <Frederick.Hirsch@nokia.com> wrote: > > 6) Contacts > > async vs non-async > > http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0134.html > (Richard) Thanks for putting this in the agenda. I just want to clarify before the call that it's not a case of async vs non-async (read: it remains all async all the time) - just that a click event will not show the intermediate asynchronous notification bar [1] but jump straight to the picker dialog [2] while an inline call (any non-click initiated action) to the same method would show the asynchronous notification bar [1] followed by the picker dialog [2]. The terminology could be revised to be clearer here if necessary. It's similar to window.open() and browser popup blockers. If window.open() is called inline then the user is notified that the popup was blocked. If window.open() is called via a user-initiated click event, the popup is opened directly. The hope is that it works without needing to maintain/publish/discuss a separate HTML Contact Sharing spec and without the need to integrate with existing HTML elements in such a strict manner. Let's discuss tomorrow. - Rich [1] http://dev.w3.org/2009/dap/contacts/contacts_notification.png (Asynchronous Contacts Notification Bar) [2] http://dev.w3.org/2009/dap/contacts/contacts_picker.png (Contacts Picker Dialog)
Received on Tuesday, 28 September 2010 23:00:07 UTC