web-platform-tests / web-platform-tests/interop
NavigationTiming - NotRestoredReasons
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 524
- Forks
- 35
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Description
The NotRestoredReasons interface of the Performance API provides report data containing reasons why the current document was blocked from using the back/forward cache (bfcache) on navigation.
The feature would enable developers to understand why their sites are not being stored in the BFCache across browsers, enabling them to make their back/forward navigations faster.
Specification
https://html.spec.whatwg.org/multipage/browsing-the-web.html#document-state-not-restored-reasons
web-feature
https://web-platform-dx.github.io/web-features-explorer/features/bfcache-blocking-reasons/
Test Links
Additional Signals
Positive Mozilla position: https://github.com/mozilla/standards-positions/issues/766
No official WebKit position: https://github.com/WebKit/standards-positions/issues/154
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked HTML specification section for document state not-restored reasons and review the web-platform-tests results for performance-timeline/not-restored-reasons. Determine the Interop coverage needed for the NotRestoredReasons interface and consider the listed browser position signals; done means the feature has appropriate cross-browser test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100