Re: Notifications WG update

To close the loop on a month-old thread (my apologies!):

It seems odd that a web author would post notifications without caring about whether the user has opted in. That appears to be use of the spec in an unintended fashion.

However, I do agree that if the user agent’s UI for asking permission from the user suffices, and no additional changes need to be made on the webpage to reflect that decision, then the callback function is unneeded, and making it optional would be an acceptable convenience.

Jon


On Feb 26, 2013, at 11:02 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Wed, Feb 27, 2013 at 12:14 AM, Jon Lee <jonlee@apple.com> wrote:
>> 2) Unlike the WHATWG spec, I do not think we should make the callback
>> parameter optional. Discussion of this issue can be found in [3], and I
>> invite continuing that discussion here if anyone has concerns.
> 
> If you just create notifications in your code and don't care about
> whether the user has opted into them or not, not having to provide the
> callback seems like a fine convenience. I think Jake argued that case
> pretty well. Reversing that decision in a distinct forum without
> addressing his substantial point is not very nice.
> 
> 
> -- 
> http://annevankesteren.nl/