Closed Bug 1568668 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 18057 - ElementTiming and LCP: add fully active check

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox70 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla70
Tracking Flags:
Tracking Status
firefox70 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Nicolás Peña Moreno <npm@chromium.org> wrote:

ElementTiming and LCP: add fully active check

The element attribute getter should only return the element when the
document is fully active. This check is done similar to other places
such as Fullscreen::RequestFullscreen. Tests are added.

Bug: 879270, 942033, 942033
Change-Id: Ie90c25ab5d07d03ccb1f9fe330d074c407aeeb7c
Reviewed-on: https://chromium-review.googlesource.com/1717238
WPT-Export-Revision: 47e1052973650375ebbb447d0bef77d4d5b4eb5c

Ran 2 tests and 2 subtests TIMEOUT: 2 NOTRUN : 2 New tests that have failures or other problems: /element-timing/element-only-when-fully-active.html: TIMEOUT Only expose element attribute for fully active documents: NOTRUN /largest-contentful-paint/element-only-when-fully-active.html: TIMEOUT Only expose element attribute for fully active documents: NOTRUN
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/d6bc55d722ac [wpt PR 18057] - ElementTiming and LCP: add fully active check, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/6972a90ee3b3 [wpt PR 18057] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/d6bc55d722ac
https://hg.mozilla.org/mozilla-central/rev/6972a90ee3b3

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