Meziantou.Frameworkperformance-timeline
editWPT coverage of the tests of performance-timeline at the revision 5602b0f210e3. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features) and the reftests are listed separately from the stable tests.
| Group | Passing | Tests | Disabled | Pass rate |
|---|---|---|---|---|
| Stable | 29 | 30 | 0 | 97% |
| Tentative | 7 | 21 | 0 | 33% |
| Reftests | 0 | 0 | 0 | – |
| All | 36 | 51 | 0 | 71% |
Failure reasons
The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.
- TEST BUG: 1
- NOT IMPLEMENTED: 14
Stable tests
Tentative tests
| Test | Result | Subtests | Kind | Description |
|---|---|---|---|---|
back-forward-cache-restoration.tentative.html | Timeout | 0 / 1 | NOT IMPLEMENTED | the back-forward-cache-restoration entry type (BackForwardCacheRestoration): no entry is queued when a document is restored from the back/forward cache |
buffered-flag-with-entryTypes-observer.tentative.any.js | Fail | 0 / 2 | NOT IMPLEMENTED | the tentative buffered option with entryTypes: observe() throws a TypeError when entryTypes is used with another member, as specified |
navigation-id-detached-frame.tentative.html | Pass | 1 / 1 | ||
navigation-id-element-timing.tentative.html | Pass | 1 / 1 | ||
navigation-id-initial-load.tentative.html | Pass | 1 / 1 | ||
navigation-id-long-task-task-attribution.tentative.html | Pass | 1 / 1 | ||
navigation-id-mark-measure.tentative.html | Pass | 1 / 1 | ||
navigation-id-reset.tentative.html | Fail | 0 / 1 | TEST BUG | the test does not wait for the reload: location.reload() navigates from a task, so the waitForPageShow and the mark of the next scripts still run in the document restored from the back/forward cache, and the second navigation id is the one of that document (the restoration does regenerate it, which the first assertion checks) |
navigation-id-resource-timing.tentative.html | Pass | 1 / 1 | ||
not-restored-reasons/performance-navigation-timing-attributes.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-bfcache-reasons-stay.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-bfcache.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-cross-origin-bfcache.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-fetch.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-iframes-without-attributes.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-navigation-failure.tentative.window.js | Pass | 1 / 1 | ||
not-restored-reasons/performance-navigation-timing-not-bfcached.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-redirect-on-history.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-reload.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-same-origin-bfcache.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |
not-restored-reasons/performance-navigation-timing-same-origin-replace.tentative.window.js | Fail | 0 / 1 | NOT IMPLEMENTED | PerformanceNavigationTiming.notRestoredReasons (the NotRestoredReasons interfaces), and RTCPeerConnection, which most tests use to make a page ineligible for the back/forward cache |