It should definitely not be necessary to call Notification.show(), although
I have not removed that API since I am busy with some other tasks
currently. What browser/WebKit revision are you using?
In Chrome 26, I just opened the javascript console and typed "new
Notification('blah')" and it displayed a notification, so it doesn't seem
like show() is necessary in more recent versions of WebKit.
On Thu, Feb 7, 2013 at 1:51 PM, Claudio Saavedra <csaave...@igalia.com>wrote:
> On Mon, 2013-01-28 at 10:35 +0100, Andrew Wilson wrote:
> > So, we've recently landed some fixes to address permissions handling
> > for Notification.show(): http://trac.webkit.org/changeset/140927
> >
> > Turns out, the notifications specification does not have a show() API
> > (the notification is automatically shown from the constructor
> > -- http://notifications.spec.whatwg.org/#api). Does anyone have any
> > objections to moving the show() API under the
> > ENABLE_LEGACY_NOTIFICATIONS flag to bring us under compliance with the
> > spec?
>
> What's the status of this? Apparently it is still necessary to call
> Notification.show() after a notification is created. Are you tracking
> this in a bug report?
>
> Claudio
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
