Skip to content

Conversation

@adamraine
Copy link
Contributor

Split off the artifact part from #14465 + added some test cases

@adamraine adamraine requested a review from a team as a code owner November 1, 2022 21:31
@adamraine adamraine requested review from connorjclark and removed request for a team November 1, 2022 21:31
@connorjclark
Copy link
Collaborator

Should we track the pageshow event's persisted state as well as these explanations?

@connorjclark
Copy link
Collaborator

  • BFCache
  • property of notRestoredReasons to match the web api
  • should be an array to account of timespans
  • but let's just consider the first not restored tree for now in the audit, and punt on potential table rendering improvements for showing multiple attempted navigations in a timespan

so like:

Array<{beforeUrl, afterUrl, notRestoredReasonsTree}>

naming up to adam tho

@adamraine adamraine changed the title core: add BFCacheErrors artifact core: add BFCache artifact Nov 10, 2022
@adamraine adamraine changed the title core: add BFCache artifact core: add BFCacheFailures artifact Nov 10, 2022
const events = [];
for (const event of context.dependencies.DevtoolsLog) {
if (event.method === 'Page.backForwardCacheNotUsed') {
events.push(event.params);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will we need the urls associated with this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Potentially in the future if we start surfacing more than one failure. In that scenario, it would be easy to add a url parameter to Artifacts.BFCacheFailure. I don't think we should worry about it right now though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants