Bug 312937
| Summary: | [Site Isolation] http/tests/security/XFrameOptions/x-frame-options-ancestors-same-origin-deny.html is failing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Anthony Tarbinian <a.tarbinian> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Anthony Tarbinian
When a cross-origin subframe is blocked by X-Frame-Options with site isolation,
two things broke compared to the non-site-isolation behavior:
1. The "Refused to display" console message was silently dropped.
2. The SecurityError changed from a sandbox-specific message to a generic
cross-origin error.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/175291706>
Anthony Tarbinian
Pull request: https://github.com/WebKit/WebKit/pull/63279
Anthony Tarbinian
Thinking about this more, I don't like adding a new field to FrameTreeSyncData just for an error message of an exception. I realized I'm not synchronizing this when the sandbox state changes so it feels a bit error-prone. Going to think of another approach.
EWS
Committed 313507@main (cbe41ae4841f): <https://commits.webkit.org/313507@main>
Reviewed commits have been landed. Closing PR #63279 and removing active labels.