[webkit-changes] [WebKit/WebKit] f6795d: WKTR should use locally built WebKit extensions al...

[Per Arne Vollan]

  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: f6795da699fa7df184f71a50a0b16d310cfbc4b0
      https://github.com/WebKit/WebKit/commit/f6795da699fa7df184f71a50a0b16d310cfbc4b0
  Author: Per Arne Vollan <pvollan at apple.com>
  Date:   2024-07-12 (Fri, 12 Jul 2024)

  Changed paths:
    M Source/WebKit/Platform/cocoa/AssertionCapability.mm
    M Source/WebKit/Shared/Cocoa/DefaultWebBrowserChecks.mm
    M Source/WebKit/UIProcess/Launcher/ProcessLauncher.h
    M Source/WebKit/UIProcess/Launcher/cocoa/ProcessLauncherCocoa.mm

  Log Message:
  -----------
  WKTR should use locally built WebKit extensions also when USE(LEGACY_EXTENSIONKIT_SPI) == 1
https://bugs.webkit.org/show_bug.cgi?id=276456
rdar://131496708

Reviewed by Chris Dumez.

WKTR should use locally built WebKit extensions also when USE(LEGACY_EXTENSIONKIT_SPI) == 1. When launching
the locally built WebKit extensions we can use the BrowserEngineKit API. This patch also fixes two debug
asserts observed when testing this.

* Source/WebKit/Platform/cocoa/AssertionCapability.mm:
* Source/WebKit/Shared/Cocoa/DefaultWebBrowserChecks.mm:
(WebKit::isInWebKitChildProcess):
* Source/WebKit/UIProcess/Launcher/ProcessLauncher.h:
* Source/WebKit/UIProcess/Launcher/cocoa/ProcessLauncherCocoa.mm:
(WebKit::ProcessLauncher::hasExtensionsInAppBundle):
(WebKit::launchWithExtensionKit):
(WebKit::LaunchGrant::LaunchGrant):
(WebKit::hasExtensionInAppBundle): Deleted.

Canonical link: https://commits.webkit.org/280916@main



To unsubscribe from these emails, change your notification settings at https://github.com/WebKit/WebKit/settings/notifications