Skip to content

docs(compatibility): document remaining extension gaps - #320

Merged
Alexays merged 1 commit into
mainfrom
docs/extension-compat-gaps
Nov 6, 2026
Merged

Alexays merged 1 commit into
mainfrom
docs/extension-compat-gaps

Conversation

@Alexays

@Alexays Alexays commented Nov 6, 2026

Copy link
Copy Markdown
Owner

Summary

Documents the extension gaps that have no generic fix in Lilo, each checked against Lilo's code and WebKit's sources:

  • Extension manifest: sandbox.pages are served like other extension pages, with the extension_pages CSP and chrome.*, so eval and new Function are refused there (new WEBKIT-GAPS entry 103 and a WebKitGapTests case; the CSP is not widened). web_accessible_resources.use_dynamic_url is ignored.
  • Missing: chrome_settings_overrides and the favicon permission (_favicon/ URLs).
  • runtime: setUninstallURL succeeds and does nothing.
  • declarativeNetRequest: getAvailableStaticRuleCount always answers 30000; exclusions compile to ignore-following-rules that also cancel the extension's later rules (WEBKIT-GAPS 104); initiatorDomains miss frames whose URL names a port (WEBKIT-GAPS 105).
  • devtools: the members WebKit's chrome.devtools lacks, in COMPATIBILITY.md and chrome-surface-gaps.txt (not probed by ChromeSurfaceTests, which still checks COMPATIBILITY.md names them). An inspector Lilo connects without showing it (chrome.debugger, agent tools) starts every extension's devtools_page.
  • commands: "global": true works only while Lilo is active; commands leaves the "Supported as in Chrome" list.
  • webRequest: no initiator, frameType or documentLifecycle, status-text-only statusLine, localized error.
  • Engine globals: JavaScriptCore gaps (Temporal, iterator helpers, version-floor gaps, Date.parse formats, webkit.org/b/242740, Error.prepareStackTrace), no polyfill.
  • Password managers: 1Password's desktop app needs Lilo added in Settings > Browser > Add Browser.

Upstream WebKit reports are worth filing for the sandbox pages' CSP, use_dynamic_url, DNR exclusion rules and initiatorDomains with ports; none is filed here.

Testing

  • make swift-test SWIFT_TEST_FILTER="LiloTests/WebKitGapTests LiloTests/ChromeSurfaceTests": passes, including the new testSandboxPagesGetTheExtensionPagesPolicyAndAPIs.
  • make swiftlint: no violations.
  • Engine claims probed with the system jsc on macOS 27.2.

List the extension gaps that have no generic fix: sandbox pages served
with the extension pages' policy, use_dynamic_url, the favicon
permission, chrome_settings_overrides, setUninstallURL, the static rule
count, DNR exclusions and initiatorDomains with ports, the partial
chrome.devtools surface, global commands, inspector connections starting
devtools pages, webRequest details, JavaScriptCore engine gaps and the
1Password desktop app step. Add a WebKitGapTests case for sandbox pages.
@Alexays
Alexays merged commit 7902c6f into main Nov 6, 2026
7 of 13 checks passed
@Alexays
Alexays deleted the docs/extension-compat-gaps branch November 6, 2026 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant