[Webkit-unassigned] [Bug 201642] [GTK][WPE] Add WebKitWebView:page-id property

[bugzilla-daemon at webkit.org]

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

Adrian Perez <aperez at igalia.com> changed:

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

--- Comment #8 from Adrian Perez <aperez at igalia.com> ---
(In reply to Michael Catanzaro from comment #7)
> Comment on attachment 379625 [details]
> Rebased patch
> 
> Exposing the messaging APIs sounds like a good idea to me, since using page
> IDs feels fragile now that we have PSON.
> 
> Still, removing page IDs completely from the API is not possible unless we
> totally give up on any pretense of backwards-compatibility and bump the API
> version. Deprecating these APIs and making them return, say, 0 would break
> too many apps. Having changing page IDs is risky enough as it is.
>
> […]

I think for the WPE port we could afford an API bump for 2.28, provided
that it's limited to a few selected changes (like this one), and that
the rest of the API remains backwards compatible. For the GTK port…
well, as you point out it's definitely trickier and I would not push
for it until a more suitable moment. I have been hoping that at some
point we are able make an API for GTK4. True, we will have to maintain
the existing code paths working as long as GTK3 remains supported, but
at least we will have a path sunsetting usage of page IDs.

Anyway, that is just a bit of a braindump which deserves more planning
and discussion. If something is clear is that we cannot afford to break
GTK applications anytime soon.

-- 
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/20190927/3c21eed9/attachment-0001.html>