-
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
Remove 'Coming Soon' results from report #1637
Conversation
:parade: |
As for followup issues:
These, along with warm reload, are longstanding features on the backlog. No issue filed for them, but they are on the periphery.
I think this was EIL, which we actually delivered. We could report ranges of EIL -- such as the EIL from FCP (or FMP) to TTI. And from TTI to the end. But I think those numbers will be of limited usefulness without a visualization (like what webpagetest does:
theres a huge section about this on the Progressive Web App Checklist that discusses how to do it right. we can't detect nearly any of that, so I'm supportive of deferring to this document.
captured in #909
I'll file a ticket for these three now. update: filed: #1639 |
Someone was recently asking for a tracking bug for "Scrolls at 60fps". Do you want to file that? |
{{#if subItem.comingSoon}} | ||
<span class="subitem-result__unknown score-unknown-bg">N/A</span> | ||
{{else if subItem.error}} | ||
{{#if subItem.error}} |
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.
maybe remove .subitem-result__unknown.
and .score-unknown-bg
now that they're unused? are there other things we're missing?
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.
Need to run the css usage gatherer against report :)
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.
We still need the unknown error background image. a067d30#diff-181e527364f32304fefacb83683da1a7R193.
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.
oh right :) so just score-unknown-bg
?
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.
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.
🙌
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
¯\_(ツ)_/¯
Say goodbye to these friends:
ref #332, #333