Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: d7e49edab1122fd458f73d06b7973439ef915b40
https://github.com/WebKit/WebKit/commit/d7e49edab1122fd458f73d06b7973439ef915b40
Author: Ben Nham <[email protected]>
Date: 2023-12-05 (Tue, 05 Dec 2023)
Changed paths:
M Source/WebKit/UIProcess/API/Cocoa/_WKWebsiteDataStoreDelegate.h
Log Message:
-----------
Define _WKWebsiteDataStoreDelegate callback methods for WindowProxy property
access
https://bugs.webkit.org/show_bug.cgi?id=265408
rdar://problem/118852728
Reviewed by David Kilzer.
We want to define some _WKWebsiteDataStoreDelegate callbacks that notify the
embedder that certain
properties on WindowProxy get accessed on windows associated with either side
of a window.open
call. This patch only defines the delegate method and doesn't include the logic
that actually calls
the method.
Basically, if a site opens another site via window.open, we will:
1. Call this new delegate method the moment that the `window.open` call occurs
with
`WKWindowProxyPropertyInitialOpen`.
2. If either side of the WindowProxy object is used via the opener
relationship, then we will call
the delegate method with one of `WKWindowProxyPropertyPostMessage`,
`WKWindowProxyPropertyClosed`,
or `WKWindowProxyPropertyOther` depending on whether the `postMessage`,
`closed`, or some other
property is called on the `WindowProxy` object respectively.
The `directly` parameter is true if this `openedRegistrableDomain` was the
domain that actually
direclty accessed `property` on the `WindowProxy` instance. Otherwise, the
`openedRegistrableDomain`
is only blamed for accessing the property because it exists in the navigation
history of the frame.
* Source/WebKit/UIProcess/API/Cocoa/_WKWebsiteDataStoreDelegate.h:
Canonical link: https://commits.webkit.org/271575@main
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
