Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 65891eced1c644c41336e7143b251cf66d1645bf
https://github.com/WebKit/WebKit/commit/65891eced1c644c41336e7143b251cf66d1645bf
Author: Anne van Kesteren <[email protected]>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
A
LayoutTests/imported/w3c/web-platform-tests/fs/FileSystemBaseHandle-postMessage-insecure-context.https.window-expected.txt
A
LayoutTests/imported/w3c/web-platform-tests/fs/FileSystemBaseHandle-postMessage-insecure-context.https.window.html
A
LayoutTests/imported/w3c/web-platform-tests/fs/FileSystemBaseHandle-postMessage-insecure-context.https.window.js
A
LayoutTests/imported/w3c/web-platform-tests/fs/resources/insecure-context-message-host.html
A
LayoutTests/imported/w3c/web-platform-tests/fs/resources/insecure-context-message-target.html
M LayoutTests/imported/w3c/web-platform-tests/fs/resources/w3c-import.log
M LayoutTests/imported/w3c/web-platform-tests/fs/w3c-import.log
M Source/WebCore/bindings/js/SerializedScriptValue.cpp
Log Message:
-----------
Do not deserialize FileSystemHandle in non-secure contexts
https://bugs.webkit.org/show_bug.cgi?id=326946
rdar://189588333
Reviewed by Youenn Fablet.
FileSystemHandle is [SecureContext], but posting one to a non-secure
context of the same origin, such as an https frame inside an http page,
delivered it there. Use the generated exposure check, through
isInterfaceExposedInGlobalObject() from 322979@main, so that those
messages fail to deserialize and result in a messageerror event.
FileSystemHandle can also be stored in IndexedDB, but a non-secure
context never shares a storage partition with a secure context of the
same origin, so there is no IndexedDB equivalent to test.
Test:
imported/w3c/web-platform-tests/fs/FileSystemBaseHandle-postMessage-insecure-context.https.window.html
Canonical link: https://commits.webkit.org/323219@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
