W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2011

[whatwg] Optional non-blocking mode for simple dialogs (alert, confirm, prompt).

From: Adam Barth <w3c@adambarth.com>
Date: Sat, 26 Feb 2011 16:08:41 -0800
Message-ID: <AANLkTimQ-yPRnVPst381Et8SOKdcAc=W50D_LB-koVgA@mail.gmail.com>
On Sat, Feb 26, 2011 at 2:29 PM, Ben Rimmington <benrimmington at me.com> wrote:
> <http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#simple-dialogs>
>
> An optional callback parameter could be added to the simple dialogs API:
>
>> result = window.alert(message, [callback]);
>>
>> result = window.confirm(message, [callback]);
>>
>> result = window.prompt(message, [default], [callback]);
>
> If the callback argument is recognised as a function value:
>
> ?* the result is the supplied callback;
>
> ?* the callee returns without waiting for user input;
>
> ?* the callback is invoked after the dialog is dismissed.
>
> Otherwise [see current spec]:
>
> ?* the callee simply ignores the callback argument;
>
> ?* the script is paused until the dialog is dismissed;
>
> ?* the result is undefined, boolean, string or null.
>
> For user agents that don't support the updated API:
>
>> function promptWrapper(message, default, callback) {
>> ? ? var result = window.prompt(message, default, callback);
>> ? ? if (callback && (typeof callback === "function")) {
>> ? ? ? ? if (result !== callback) {
>> ? ? ? ? ? ? callback(result);
>> ? ? ? ? }
>> ? ? ? ? return callback;
>> ? ? }
>> ? ? return result;
>> }

Of course, that would be a synchronous callback rather than an async one...

Adam


> I'm not sure if navigator.yieldForStorageUpdates() is needed in the non-blocking mode.
>
>
Received on Saturday, 26 February 2011 16:08:41 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC