-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
synchronously use same origin-domain in iframe check #107
base: main
Are you sure you want to change the base?
Conversation
Updated WebKit: WebKit/WebKit#13389 I'll update the WPTests also to add a specific same origin-domain check. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
… same origin-domain as top-origin https://bugs.webkit.org/show_bug.cgi?id=256241 rdar://107109904 Reviewed by NOBODY (OOPS!). Now does same origin-domain check against top-level origin. Relevant spec change: w3c/badging#107 * LayoutTests/imported/w3c/web-platform-tests/badging/setAppBadge_cross_origin.sub.https-expected.txt: * Source/WebCore/page/Navigator.cpp: (WebCore::Navigator::setAppBadge):
Closes #106
Now checks "same origin-domain" instead of the more restrictive "same origin".
This change:
Implementation commitment (delete if not making normative changes):
Person merging, please make sure that commits are squashed with one of the following as a commit message prefix: