Skip to content

Fix webkit per window schemes - #186

Merged
5cript merged 2 commits into
mainfrom
fix/webkit-per-window-schemes
Oct 18, 2026
Merged

5cript merged 2 commits into
mainfrom
fix/webkit-per-window-schemes

Conversation

@5cript

@5cript 5cript commented Oct 18, 2026

Copy link
Copy Markdown
Member
  • WebKitGTK takes one handler per scheme name and web context, a second window's registration was refused and its requests went to the first window's handler
  • A window without the scheme gets a network error, closing the window that registered a scheme first no longer leaves the context with its freed handler

…esting web view

- WebKitGTK takes one handler per scheme name and web context, a second window's registration was refused and its requests went to the first window's handler
- A window without the scheme gets a network error, closing the window that registered a scheme first no longer leaves the context with its freed handler
…e WebView2 registration rule

- Windows needs the same scheme registrations in every window of a process, they are options of the shared browser process
@5cript
5cript merged commit 6219994 into main Oct 18, 2026
18 checks passed
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