long-animation-frame

edit

WPT coverage of the tests of long-animation-frame at the revision c8fa86fb13d4. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features), the reftests and the crash tests are listed separately from the stable tests.

GroupPassingTestsDisabledPass rate
Stable3240080%
Tentative11308%
Reftests000–
Crash tests000–
All3353062%

Failure reasons

The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.

  • NOT IMPLEMENTED: 18
  • TEST RUNNER: 2

Stable tests

TestResultSubtestsKindDescription
loaf-basic.htmlPass5 / 5
loaf-blocking-duration.htmlPass4 / 4
loaf-bound-function-opaque-sanitization.htmlPass1 / 1
loaf-buffered.htmlPass2 / 2
loaf-container-queries.htmlPass6 / 6
loaf-cross-origin-isolated.https.htmlPass1 / 1
loaf-duration-clamping.htmlPass1 / 1
loaf-event-blocking-duration.htmlPass1 / 1
loaf-event-listener.htmlPass5 / 5
loaf-first-ui-event.htmlFail4 / 5TEST RUNNERtest_driver.send_keys() dispatches the key events synchronously, while the script that calls it runs: the keydown listener runs in the script entry point of that script (https://w3c.github.io/long-animation-frames/#create-script-entry-point records nothing while a script is pending), so no INPUT.onkeydown script is reported; a browser dispatches them from the task of the user interaction
loaf-forced-layout-duration.htmlFail5 / 6NOT IMPLEMENTEDthe subtest forcedLayoutDuration and forcedStyleAndLayoutDuration are strictly positive after heavy forced layout work: the library does not measure the time it spends on the styles and the layout: styleDuration, layoutDuration and the forced*Duration of the scripts are 0 (with the virtual clock of the runner, which only advances when it is read, they would be 0 anyway)
loaf-forced-style-duration.htmlFail4 / 5NOT IMPLEMENTEDthe subtest forcedStyleDuration and forcedStyleAndLayoutDuration are strictly positive after heavy forced style work: the library does not measure the time it spends on the styles and the layout: styleDuration, layoutDuration and the forced*Duration of the scripts are 0 (with the virtual clock of the runner, which only advances when it is read, they would be 0 anyway)
loaf-idle.htmlPass1 / 1
loaf-iframe-crossorigin.htmlPass2 / 2
loaf-iframe-same-origin.htmlPass2 / 2
loaf-iframe-self.htmlPass3 / 3
loaf-layout-duration.htmlFail7 / 8NOT IMPLEMENTEDthe subtest Heavy render-phase layout produces strictly positive layoutDuration: the library does not measure the time it spends on the styles and the layout: styleDuration, layoutDuration and the forced*Duration of the scripts are 0 (with the virtual clock of the runner, which only advances when it is read, they would be 0 anyway)
loaf-onmessage.htmlPass6 / 6
loaf-paint-mixin.htmlFail0 / 1NOT IMPLEMENTEDthe library has no presentation time: the presentationTime of the frames is null (https://w3c.github.io/paint-timing/#dom-painttimingmixin-presentationtime), and the test expects it after paintTime
loaf-pause-duration.htmlFail1 / 2TEST RUNNERa synchronous request of a window blocks the thread that advances the virtual clock: the runner answers delay.py?ms=180 without delay, so the synchronous XMLHttpRequest does not pause the script (pauseDuration is 0) and the script does not last 360 ms
loaf-pointer-without-render-iframe.htmlPass1 / 1
loaf-pointer-without-render.htmlPass1 / 1
loaf-popup.htmlPass1 / 1
loaf-promise-scheduled-render.htmlPass1 / 1
loaf-promise.htmlPass5 / 5
loaf-script-block.htmlFail9 / 10NOT IMPLEMENTEDthe subtest of the module imported by import(): the engine evaluates the imported module in a reaction of the promise of the import, without a host hook, so its evaluation is reported in the resolve-promise script of the import (import.then), not as a module-script
loaf-script-detached-window.htmlPass1 / 1
loaf-script-nested-callback.htmlPass2 / 2
loaf-script-window-attribution.htmlPass7 / 7
loaf-source-location-redirect.htmlPass12 / 12
loaf-source-location.htmlPass5 / 5
loaf-stream.htmlPass3 / 3
loaf-style-and-layout-duration-bounds.htmlPass3 / 3
loaf-style-duration.htmlFail9 / 10NOT IMPLEMENTEDthe subtest Heavy render-phase style recalculation produces strictly positive styleDuration: the library does not measure the time it spends on the styles and the layout: styleDuration, layoutDuration and the forced*Duration of the scripts are 0 (with the virtual clock of the runner, which only advances when it is read, they would be 0 anyway)
loaf-supportedEntryTypes.htmlPass1 / 1
loaf-timeline.htmlPass1 / 1
loaf-toJSON.htmlPass1 / 1
loaf-ui-event-render-start.htmlPass1 / 1
loaf-user-callback.htmlPass10 / 10
loaf-visibility.htmlPass2 / 2

Tentative tests

TestResultSubtestsKindDescription
conditional-measure-iframe-time-origin.tentative.htmlError0 / 0NOT IMPLEMENTEDthe conditional user timing of the long animation frames (performance.markConditional(), performance.measureConditional() and userTimingEntries), a Chromium experiment that the specification does not define
conditional-measure-time-resolve.tentative.htmlError0 / 0NOT IMPLEMENTEDthe conditional user timing of the long animation frames (performance.markConditional(), performance.measureConditional() and userTimingEntries), a Chromium experiment that the specification does not define
conditional-user-timing-basic.tentative.htmlError0 / 0NOT IMPLEMENTEDthe conditional user timing of the long animation frames (performance.markConditional(), performance.measureConditional() and userTimingEntries), a Chromium experiment that the specification does not define
conditional-user-timing-buffer-limit.tentative.htmlError0 / 0NOT IMPLEMENTEDthe conditional user timing of the long animation frames (performance.markConditional(), performance.measureConditional() and userTimingEntries), a Chromium experiment that the specification does not define
conditional-user-timing-cross-origin-measure.tentative.htmlError0 / 0NOT IMPLEMENTEDthe conditional user timing of the long animation frames (performance.markConditional(), performance.measureConditional() and userTimingEntries), a Chromium experiment that the specification does not define
conditional-user-timing-cross-origin.tentative.htmlError0 / 0NOT IMPLEMENTEDthe conditional user timing of the long animation frames (performance.markConditional(), performance.measureConditional() and userTimingEntries), a Chromium experiment that the specification does not define
conditional-user-timing-detached-window.tentative.htmlError0 / 0NOT IMPLEMENTEDthe conditional user timing of the long animation frames (performance.markConditional(), performance.measureConditional() and userTimingEntries), a Chromium experiment that the specification does not define
conditional-user-timing-same-origin.tentative.htmlError0 / 0NOT IMPLEMENTEDthe conditional user timing of the long animation frames (performance.markConditional(), performance.measureConditional() and userTimingEntries), a Chromium experiment that the specification does not define
loaf-congested-moment-worker.tentative.htmlTimeout0 / 5NOT IMPLEMENTEDthe long animation frames of the dedicated workers (the congested moments), a Chromium experiment (LongAnimationFrameWorker) that the specification does not define
loaf-promise-import.tentative.htmlPass1 / 1
loaf-script-count.tentative.htmlFail0 / 2NOT IMPLEMENTEDscriptCount, a Chromium experiment (LongAnimationFrameWorker) that the specification does not define
loaf-stream-source-location.tentative.htmlFail0 / 1NOT IMPLEMENTEDthe promises of the platform have no creation-time attribution (optional, https://w3c.github.io/long-animation-frames/#webidl-monkey-patches): the reactions of the promises of the streams are reported as Promise.then, without source location, not as StreamPromise.resolve.then
performance-bind.tentative.htmlFail0 / 4NOT IMPLEMENTEDperformance.bind() (the user-entry-point scripts), a Chromium experiment that the specification does not define