I agree that this will be quite disruptive. I think it would be advantageous to deprecate the InjectedBundle APIs asap. At least for the next year (and likely a little longer) we will need to keep a working configuration without site isolation. In the very long term we probably don’t want to keep them working, but I’m not sure exactly what that time frame looks like right now. I’m not saying it’ll be a sudden change, but it is going to be a big change with big consequences that we need to start preparing for now.
> On Aug 12, 2022, at 2:29 PM, Michael Catanzaro <mcatanz...@gnome.org> wrote: > > On Fri, Aug 12 2022 at 01:40:02 PM -0700, Alex Christensen via webkit-dev > <webkit-dev@lists.webkit.org> wrote: >> Would the maintainers of the GTK and WPE APIs be willing to assist in >> migrating from those APIs and designing replacements in the UI process? > > Sigh... we'll need to discuss what to do. Unfortunately, these are public > APIs and this will be extremely disruptive. If it's needed for site > isolation, I don't see that we have much choice. But if we remove these APIs, > Linux distros will get stranded on the last version of WebKit that still > supports them and will be unable to take our further updates. > > Deprecation is a lot easier than removal. If we can keep deprecated APIs > working and just disable site isolation when they're used, that would be much > less disruptive. > > Michael > > _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
