Closed Bug 1469040 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 11534 - [Mojo Blob URLs] Make clicking an <a target="blank_"> with a blob URL work correctly.

Categories

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

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

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla63
Tracking Flags:
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream]) 

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

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

Marijn Kruisselbrink <mek@chromium.org> wrote:
>  [Mojo Blob URLs] Make clicking an <a target="blank_"> with a blob URL work correctly.
>  
>  This goes through a code-path where the blob URL token was incorrectly
>  dropped, so make sure we copy the token from the old FrameLoadRequest to
>  the new FrameLoadRequest.
>  
>  Adds a web-platform-test to verify this behavior, and enables the blob URL browser
>  tests to also run with MojoBlobURLs enabled. This browser test required another
>  bug fix in RenderFrameHostImpl.
>  
>  Cq-Include-Trybots: luci.chromium.try:linux_mojo
>  Bug: 800901
>  Change-Id: I87eee70e784dd8cb273f8671f37b00d8a93d9543
>  Reviewed-on: https://chromium-review.googlesource.com/1102820
>  WPT-Export-Revision: 490aa607d27599ef84acca6f888622004c1323e6
Component: web-platform-tests → DOM
Product: Testing → Core
Ran 1 tests and 6 subtests
OK     : 1
PASS   : 6
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/80fb571c93e2
[wpt PR 11534] - [Mojo Blob URLs] Make clicking an <a target="blank_"> with a blob URL work correctly., a=testonly
https://hg.mozilla.org/mozilla-central/rev/80fb571c93e2
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.