[wpt-sync] Sync PR 13235 - Use adjusted relatedTarget on WindowEventContext

RESOLVED FIXED in Firefox 64

Status

enhancement
P4
normal
RESOLVED FIXED
11 months ago
11 months ago

People

(Reporter: wptsync, Unassigned)

Tracking

unspecified
mozilla64
Points:
---

Firefox Tracking Flags

(firefox64 fixed)

Details

(Whiteboard: [wptsync downstream], )

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

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

Rakina Zata Amni <rakina@chromium.org> wrote:
>  Use adjusted relatedTarget on WindowEventContext
>  
>  In event capturing phase, when the event is dispatched on window, the
>  related target was not set properly (it uses the state of the event
>  at the target, which means related target is the same as when it was
>  at the target). This might cause leaks when the event's relatedTarget
>  is inside a shadow tree. This change makes it so at window context,
>  the relatedTarget used is the relatedTarget of the last
>  NodeEventContext.
>  
>  Bug: 817222
>  Change-Id: I1edea3977202b0a05e3e8ea46a5b8c1edb4b834d
>  Reviewed-on: https://chromium-review.googlesource.com/1248244
>  WPT-Export-Revision: 86f51f494cf241e73d8dfb3aadd857adc172b86d
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 1 tests and 2 subtests
OK     : 1
PASS   : 2
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/b8df96831cdb
[wpt PR 13235] - Use adjusted relatedTarget on WindowEventContext, a=testonly
https://hg.mozilla.org/mozilla-central/rev/b8df96831cdb
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in before you can comment on or make changes to this bug.