Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the unload listener #68

Merged
merged 1 commit into from
Jul 24, 2020
Merged

Remove the unload listener #68

merged 1 commit into from
Jul 24, 2020

Conversation

philipwalton
Copy link
Member

This PR fixes #67 by switching from unload to beforeunload. Both events work to address this Chrome bug, but the beforeunload event won't fail the new no-unload-listeners Lighthouse audit.

@philipwalton philipwalton merged commit 7b88555 into master Jul 24, 2020
@philipwalton philipwalton deleted the remove-unload branch July 24, 2020 01:24
kodiakhq bot pushed a commit to vercel/next.js that referenced this pull request Sep 12, 2020
ref GoogleChrome/web-vitals#68

won't fail the new [`no-unload-listeners`](GoogleChrome/lighthouse#11085) Lighthouse audit.
HitoriSensei pushed a commit to HitoriSensei/next.js that referenced this pull request Sep 26, 2020
ref GoogleChrome/web-vitals#68

won't fail the new [`no-unload-listeners`](GoogleChrome/lighthouse#11085) Lighthouse audit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unload event listeners should not be used
1 participant