Closed Bug 1440584 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 9644 - 'navigate-to' directive tests

Categories

(Core :: DOM: Security, enhancement, P3)

Product:
Core
Component:
DOM: Security
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla61
Tracking Flags:
Tracking Status
firefox61 --- fixed

People

(Reporter: mozilla.org, Unassigned)

Details

(Whiteboard: [wptsync downstream][domsecurity-backlog3]) 

Sync web-platform-tests PR 9644 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/w3c/web-platform-tests/pull/9644
Details from upstream follow.

Andy Paicu wrote:
>  'navigate-to' directive tests
>  
>  PR: https://github.com/w3c/webappsec-csp/pull/290
>  
>  Bug: 805886
>  Change-Id: I5bdda65c7e70e729b33a3647135fee6453e97e66
>  Reviewed-on: https://chromium-review.googlesource.com/934181
>  WPT-Export-Revision: 5e6635f2de49406246150474a96c6eed5046cf85
Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog3]
Whiteboard: [wptsync downstream][domsecurity-backlog3] → [wptsync downstream error][domsecurity-backlog3]
Whiteboard: [wptsync downstream error][domsecurity-backlog3] → [wptsync downstream][domsecurity-backlog3]
Ran 28 tests and 28 subtests
OK     : 27
PASS   : 14
FAIL   : 13
TIMEOUT: 1
NOTRUN : 1

New tests that have failures or other problems:
/content-security-policy/navigate-to/child-navigates-parent-blocked.html
    Test that the parent can navigate the child because the relevant policy belongs to the navigation initiator (in this case the parent): FAIL
/content-security-policy/navigate-to/form-blocked.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/form-cross-origin-blocked.sub.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/form-redirected-blocked.sub.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/href-location-blocked.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/href-location-cross-origin-blocked.sub.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/href-location-redirected-blocked.sub.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/link-click-blocked.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/link-click-cross-origin-blocked.sub.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/link-click-redirected-blocked.sub.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/meta-refresh-blocked.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/meta-refresh-cross-origin-blocked.sub.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/meta-refresh-redirected-blocked.sub.html
    Test that the child iframe navigation is blocked: FAIL
/content-security-policy/navigate-to/parent-navigates-child-blocked.html: TIMEOUT
    Test that the parent can't navigate the child because the relevant policy belongs to the navigation initiator (in this case the parent): NOTRUN
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f9f41a459b9a
[wpt PR 9644] - 'navigate-to' directive tests, a=testonly
https://hg.mozilla.org/mozilla-central/rev/f9f41a459b9a
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox61: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in before you can comment on or make changes to this bug.