Closed Bug 1541535 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 16034 - Send `Sec-Fetch-Mode: nested-navigate` for nested navigations.

Categories

(Core :: DOM: Core & HTML, defect, P4)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla68
Tracking Flags:
Tracking Status
firefox68 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Mike West <mkwst@chromium.org> wrote:

Send Sec-Fetch-Mode: nested-navigate for nested navigations.

As defined in the Fetch Metadata spec, the Sec-Fetch-Mode header
should have a value of nested-navigate when sending a request meant to
be committed into a nested browsing context. This patch implements that
value.

Bug: 945092
Change-Id: Ibacb5bd27b7c5b17ec3d373f5d439fad2e0ac784
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536179
Reviewed-by: Arthur Sonzogni \<arthursonzogni@chromium.org>
Commit-Queue: Mike West \<mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643796}

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8ae7f21488b2
[wpt PR 16034] - Send `Sec-Fetch-Mode: nested-navigate` for nested navigations., a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8b27384446fb
[wpt PR 16034] - Send `Sec-Fetch-Mode: nested-navigate` for nested navigations., a=testonly

https://hg.mozilla.org/mozilla-central/rev/8ae7f21488b2
https://hg.mozilla.org/mozilla-central/rev/8b27384446fb

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox68: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.