Closed Bug 1854971 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 42114 - [Clipboard API] Removing substring of unsanitized HTML payload

Categories

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

task

Tracking

()

RESOLVED FIXED
120 Branch
Tracking Status
firefox120 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Ana SollanoKim <ansollan@microsoft.com> wrote:

[Clipboard API] Removing substring of unsanitized HTML payload

Previously, for unsanitized HTML, we returned the payload between the start and end fragment tags, using the fragment_start and fragment_end values. However, other applications can have important information that directly affects the payload outside of the fragment tags, so in this CL the substring is removed from the original payload read from the clipboard.

Bug: 1469425
Change-Id: Id75848739c9ed9d2e00de29ef8d8161f8b5731ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4779949
Reviewed-by: Evan Stade \<estade@chromium.org>
Commit-Queue: Ana Sollano Kim \<ansollan@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1200494}

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
PASS: 1

Safari

OK : 1
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by csabou@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/58d8cbd3f28a [wpt PR 42114] - [Clipboard API] Removing substring of unsanitized HTML payload, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch
You need to log in before you can comment on or make changes to this bug.