[Webkit-unassigned] [Bug 163366] [GTK] No way for applications to set notification permissions without waiting for permission request

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 26 11:48:09 PDT 2016


https://bugs.webkit.org/show_bug.cgi?id=163366

Michael Catanzaro <mcatanzaro at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mcatanzaro at igalia.com

--- Comment #3 from Michael Catanzaro <mcatanzaro at igalia.com> ---
What's going wrong is that checking Notification.permission via JavaScript does not trigger a WebKitNotificationPermissionRequest (nor should it). The sites where notification permissions work properly simply don't check this property. If http://www.bennish.net/web-notifications.html were to attempt to tell you if notifications are authorized without creating a permission request (via Notification.requestPermission()), then it would say that notifications are not authorized (even though the permission request would be automatically granted by the application. WebKit already has a means to prepopulate notification permissions (see comment #0) that we need to expose in the WebKitGTK+ API.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161026/77a98fb8/attachment.html>


More information about the webkit-unassigned mailing list