W3C home > Mailing lists > Public > public-tracking@w3.org > March 2012

Re: JS Exception API

From: Roy T. Fielding <fielding@gbiv.com>
Date: Wed, 7 Mar 2012 05:25:46 -0800
Cc: Jonathan Mayer <jmayer@stanford.edu>, Tom Lowenthal <tom@mozilla.com>, "public-tracking@w3.org" <public-tracking@w3.org>, Andy Zeigler <andyzei@microsoft.com>
Message-Id: <0BDEC452-F8EB-41C5-BDF7-4CF3929D7528@gbiv.com>
To: Nicholas Doty <npdoty@w3.org>
On Mar 6, 2012, at 4:25 PM, Nicholas Doty wrote:

> On Feb 29, 2012, at 12:38 PM, Jonathan Mayer wrote:
> 
>> Minor suggestion for adding at the end of the "JavaScript API for site-specific exceptions" section:
>> 
>> The `callback` function may not be called.  For example, the user may decline to express a preference, dismiss the exception request, or close the browser window.
> 
> That's a good point. We could change this guidance:
> 
>>          A user agent MAY use an interactive method to ask the user about
>>          their preferences, so sites SHOULD NOT assume that the callback
>>          function will be called immediately.
> 
> to:
> 
>> A user agent MAY use an interactive method to ask the user about their preferences, so sites SHOULD NOT assume that the callback function will be called immediately or at all. For example, the user may dismiss the exception request or close the browser window.

Closing the browser window I can understand, but why wouldn't
the callback be made as false if the request is dismissed?
It makes the API pretty pointless if the page logic
cannot rely on an answer and yet the window remains open.

....Roy
Received on Wednesday, 7 March 2012 13:26:17 UTC

This archive was generated by hypermail 2.3.1 : Friday, 21 June 2013 10:11:26 UTC