Closed Bug 1622011 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 22218 - [Trusted Types] Fix script handling for XML Documents.

Categories

(Core :: DOM: Security, task, P4)

Product:
Core
Component:
DOM: Security
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla76
Tracking Flags:
Tracking Status
firefox76 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

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

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

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

Daniel Vogelheim <vogelheim@chromium.org> wrote:

[Trusted Types] Fix script handling for XML Documents.

XMLDocumentParser::UpdateLeafTextNode calls CharacterData::appendData (rather
than CharacterData::ParserAppendData), which means this change is incorrectly
attributed to a user script. Additionally, CharacterData::DidModifyData now
passes UpdateSource correctly to the ChildrenChange event.

Bug: 1060949
Change-Id: Ida8c93bc68f66da45221a8490b84b669898b084f

Reviewed-on: https://chromium-review.googlesource.com/2100928
WPT-Export-Revision: e7edaeaa2a509848cf025cca9f1fd763a763c4ef

Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Whiteboard: [wptsync downstream][domsecurity-backlog] → [wptsync downstream]

CI Results

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

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
PASS : 1

Chrome

TIMEOUT: 1

Links

GitHub PR Head
GitHub PR Base

Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/66de3172be9b
[wpt PR 22218] - [Trusted Types] Fix script handling for XML Documents., a=testonly

https://hg.mozilla.org/mozilla-central/rev/66de3172be9b

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