[Webkit-unassigned] [Bug 61140] [GTK][WK2] Add HTML5 Notifications support

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Feb 11 09:01:28 PST 2013


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





--- Comment #72 from Claudio Saavedra <csaavedra at igalia.com>  2013-02-11 09:03:39 PST ---
(In reply to comment #71)
> Created an attachment (id=187590)
 --> (https://bugs.webkit.org/attachment.cgi?id=187590&action=review) [details]
> Patch

This patch implements a very basic support for notifications in WK2. It is completely independent from the previous patches.

For this to work, one needs to compile webkit using build-webkit --notifications. Right now, there are no webpages that I know of implementing the latest Web Notifications spec (as defined in http://notifications.spec.whatwg.org ), so I crafted a very simple test ( http://people.gnome.org/~csaavedra/notification.html ).

Some things that are missing or could be improved:

- There is no support yet for notification icons. A notification might have an icon (specified by a URL), in which case the implementation should fetch it and pass a GdkPixbuf to libnotify. I am not sure how to implement this, as I think it would be wise to cache this somehow.

- The libnotify specific code is all in WebKit2/API/gtk/WebKitNotificationProvider.cpp. We could abstract this and add a LibnotifyNotificationProvider that would go into Platform instead, and make WebKitNotificationProvider subclassable, so that applications could implement their own providers, independent from libnotify. In general, I think the whole API is up for discussion, as you can see the patch this is still pretty bare.

- I am abusing g_object_set_data() in order to store the NotificationID in the NotifyNotification. I suppose we might want to add a class that would wrap NotifyNotification or something like that, not to depend on those implementation details.

That's all I can think of for now.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list