[Webkit-unassigned] [Bug 243659] [GTK][WPE] Expose notifications without a page in public API

[bugzilla-daemon at webkit.org]

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

Patrick Griffis <pgriffis at igalia.com> changed:

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

--- Comment #2 from Patrick Griffis <pgriffis at igalia.com> ---
(In reply to Michael Catanzaro from comment #1)
> The downside is this would be our first global API that is not associated
> with a WebKitWebContext, which breaks the illusion that it's a true library
> context object and you can have separate instances of WebKit running if you
> have multiple WebKitWebContext objects. That doesn't seem to be avoidable,
> but maybe we could design it so that it looks like it's a property of the
> WebKitWebContext even though it's not really? We could have
> webkit_web_context_get_notification_manager() and it would just return the
> same WebKitNotificationManager regardless of which WebKitWebContext you are
> using, but maybe 10 years from now if internals change it would be possible
> to revisit that without needing another API break. On the other hand, maybe
> that's overengineering.

My thoughts are probably the closer the API is to WebKit internals the better for everybody. Less WebKitGTK complication, more robust to WebKit changes, etc.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220808/66cc57b8/attachment-0001.htm>