servo/tests/wpt/meta/content-security-policy/frame-src/frame-src-blocked.sub.html.ini
Tim van der Lippe ed469fe72f
Propagate destination through load_data (#37020)
This way, we don't always set the destination to Document (which is as
the spec is written today). Instead, we set it it in the load_data,
depending on which context we load it from.

Doing so allows us to set the `Destination::IFrame` for navigations in
iframes, enabling all frame-related CSP checks.

While we currently block iframes when `frame-src` or `child-src` is set,
their respective tests don't pass yet. That's because we don't yet
handle the cases
where we fire the correct `load` event.

Also update one WPT test to correctly fail, rather than erroring. That's
because it was using the wrong JS test variable.

Part of #4577

Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com>
Co-authored-by: Josh Matthews <josh@joshmatthews.net>
2025-05-17 08:22:11 +00:00

3 lines
143 B
INI
Vendored

[frame-src-blocked.sub.html]
[Expecting logs: ["PASS IFrame #1 generated a load event.","violated-directive=frame-src"\]]
expected: FAIL