-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
docs(audits): distinguish document.write() audit from intervention #9644
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* - Lighthouse doesn't report here on that situation, though it'll show up in `errors-in-console` | ||
* The intercention may also not block the .write() (because the connection wasn't slow), | ||
* but it will emit a console warning. | ||
* - Lighthouse doesn't highlight this here or in errors-in-console. (TODO: it probably should?). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good call. my mistake lighthouse does report these just fine. fixed and added a demo URL so we can test it out easy.
Co-Authored-By: Patrick Hulce <[email protected]>
Co-Authored-By: Patrick Hulce <[email protected]>
Co-Authored-By: Patrick Hulce <[email protected]>
Co-Authored-By: Patrick Hulce <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems destined to get out of sync with the intervention implementation but LGTM to have it somewhere :)
this resulted from some back-n-forth with @mfriesenhahn