Closed Bug 1615520 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 21796 - Make external/wpt/css/cssom-view/elementFromPoint.html robust on browsers

Categories

(Core :: DOM: CSS Object Model, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla75
Tracking Status
firefox75 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Yoshifumi Inoue <yosin@chromium.org> wrote:

Make external/wpt/css/cssom-view/elementFromPoint.html robust on browsers

This patch changes "elementFromPoint.html" to call |getBoundingClientRect()|
on \<img> instead of \<area> because all browsers returns different value for
\<area>, maybe size-less inline element, for improving robustness of test.

Because test itself verifies |elementFromPoint()| instead of
|getBoundingClientRect()|, this patch doesn't change testing

Change-Id: I40fc2c6c9cef696dc5c9f3428913b2d73ffaf5f6

Reviewed-on: https://chromium-review.googlesource.com/2054472
WPT-Export-Revision: 50947ebaff98e57ffe08b6505e3e2c834cfe3bf6

Component: web-platform-tests → DOM: CSS Object Model
Product: Testing → Core

CI Results

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

Total 1 tests and 11 subtests

Status Summary

Firefox

OK : 1
PASS: 10
FAIL: 1

Chrome

OK : 1
PASS: 11

Safari

OK : 1
PASS: 11

Links

GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

/css/cssom-view/elementFromPoint.html
Image Maps: FAIL

New Tests That Don't Pass

/css/cssom-view/elementFromPoint.html
Image Maps: FAIL (Chrome: PASS, Safari: PASS)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3c8d3984983f
[wpt PR 21796] - Make external/wpt/css/cssom-view/elementFromPoint.html robust on browsers, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
You need to log in before you can comment on or make changes to this bug.