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

report: new audit list display, indexes & new icons #5109

Merged
merged 22 commits into from
May 4, 2018

Conversation

@paulirish paulirish mentioned this pull request May 4, 2018
82 tasks
@patrickhulce
Copy link
Collaborator

patrickhulce commented May 4, 2018

review on its way, but few UI comments before I forget:

  • we're planning on bringing the numbering to opportunities too, right? paul says yes
  • there doesn't seem to be a dropdown indicator for the "Passed audits" and manual audits, I wouldn't expect I'd be able to click on them
  • I am lovin' display value now-a-days!
  • Don't think we need to do this immediately, but it'd make more sense IMO if they numbers on the audits continued counting across audit groups in a11y (like how we say the total # of passed audits/not applicable)

@vinamratasingal-zz
Copy link

vinamratasingal-zz commented May 4, 2018

+1 to Patrick's comments around adding dropdown arrows to the opportunities + manual audits + passed audits- i think that might impede discoverability.

cc: @hwikyounglee

.filter(audit => audit.group === 'diagnostics' && audit.result.score < 1);
.filter(audit => audit.group === 'diagnostics' && audit.result.score < 1)
.sort((a, b) => {
const scoreA = a.result.informative ? 100 : a.result.score;
Copy link
Collaborator

@patrickhulce patrickhulce May 4, 2018

Choose a reason for hiding this comment

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

just a heads up to line up with #5105 whoever lands first 🐎 🚗 🏁

Choose a reason for hiding this comment

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

re:@vinamratasingal's comment on dropdown -- I think once we get the overall left/right alignments on the layout, and the dropdown color being darker as intended, it would look better. Keeping watching out for any issues though!

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

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

lookin' real good 👍

--pass-icon-url: url('data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48"><title>check</title><path fill="hsl(139, 70%, 30%)" d="M24 4C12.95 4 4 12.95 4 24c0 11.04 8.95 20 20 20 11.04 0 20-8.96 20-20 0-11.05-8.96-20-20-20zm-4 30L10 24l2.83-2.83L20 28.34l15.17-15.17L38 16 20 34z"/></svg>');
--average-icon-url: url('data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48"><title>info</title><path fill="hsl(31, 100%, 45%)" d="M24 4C12.95 4 4 12.95 4 24s8.95 20 20 20 20-8.95 20-20S35.05 4 24 4zm2 30h-4V22h4v12zm0-16h-4v-4h4v4z"/></svg>');
--fail-icon-url: url('data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48"><title>warn</title><path fill="hsl(1, 73%, 45%)" d="M2 42h44L24 4 2 42zm24-6h-4v-4h4v4zm0-8h-4v-8h4v8z"/></svg>');
--collapsed-triangle-icon-url: url('data:image/svg+xml;utf8,<svg width="12" height="12" viewBox="0 0 12 12" xmlns="http://www.w3.org/2000/svg"><g fill="none" fill-rule="evenodd"><path fill="none" d="M0 0h12v12H0z"/><path fill="hsl(0, 0%, 60%)" d="M3 2l6 4-6 4z"/></g></svg>');
Copy link
Collaborator

Choose a reason for hiding this comment

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

what are these? triangle makes me think of the alert/fail icon

it looks like toggle-arrow is the chevron?

maybe we need some comments :)

@@ -462,7 +446,7 @@ summary {

.lh-load-opportunity__stats {
text-align: right;
flex: 0 0 var(--lh-audit-score-width);
flex: 0 0 calc(5 * var(--body-font-size));
Copy link
Collaborator

Choose a reason for hiding this comment

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

why the drive by calc now? is the real width not in a var anymore?

Copy link
Member Author

Choose a reason for hiding this comment

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

just a temporary solution till i take on opportunity display. :)

.lh-score__value--fail::after {
background: var(--fail-icon-url) no-repeat center center / 12px 12px;
.lh-audit--informative .lh-audit__display-text {
color: hsl(216, 5%, 39%);
Copy link
Collaborator

Choose a reason for hiding this comment

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

are we going to reuse this color? it's a gray? css var perhaps then :)

@paulirish
Copy link
Member Author

feedback addressed. bumped the surge reports, too.

@paulirish
Copy link
Member Author

we're planning on bringing the numbering to opportunities too, right?

yes, separate PR.

there doesn't seem to be a dropdown indicator for the "Passed audits" and manual audits, I wouldn't expect I'd be able to click on them

added. and added in the "4 audits" count as well. :)

Don't think we need to do this immediately, but it'd make more sense IMO if they numbers on the audits continued counting across audit groups in a11y (like how we say the total # of passed audits/not applicable)

definitely want to do this. but categoryRenderer doesn't make it easy. so i'll leave it until the file isn't so volatile.

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

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

code LGTM! just some text 🚲 🏠

report's lookin' great!!

let totalBootupTime = 0;
/** @type {Object<string, Object<string, number>>} */
const extendedInfo = {};
const devtoolsTimelineModel = await artifacts.requestDevtoolsTimelineModel(trace);
Copy link
Collaborator

Choose a reason for hiding this comment

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

rebase noise?

Copy link
Member Author

Choose a reason for hiding this comment

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

yah definitely. weird that it shows up. in the diff. I didn't touch these. :/

@@ -161,8 +166,8 @@ class CategoryRenderer {
*/
_renderFailedAuditsSection(elements) {
const failedElem = this.renderAuditGroup({
title: `${this._getTotalAuditsLength(elements)} Failed Audits`,
}, {expandable: false});
title: `Failed audits`,
Copy link
Collaborator

Choose a reason for hiding this comment

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

aww I liked them caps'd :(

Copy link
Member Author

Choose a reason for hiding this comment

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

mocks say no to Title Case. :)
cc @hwikyounglee

@@ -187,8 +192,8 @@ class CategoryRenderer {
*/
_renderNotApplicableAuditsSection(elements) {
const notApplicableElem = this.renderAuditGroup({
title: `${this._getTotalAuditsLength(elements)} Not Applicable Audits`,
}, {expandable: true});
title: `Not applicable`,
Copy link
Collaborator

Choose a reason for hiding this comment

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

why make this different from "Passed/Failed audits" we should remove from all if that's what we want, I'm cool with that 👍

Copy link
Member Author

Choose a reason for hiding this comment

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

cc @hwikyounglee

i was going off the mocks. I don't mind either way, but i do enjoy the brevity.

image

Choose a reason for hiding this comment

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

Good points. Happy for now with the current state. // Being said, we'll soon have a chance to polish the UI strings further (recently started sharing the latest mocks with the UX Writer for advice.

@paulirish paulirish merged commit af87207 into master May 4, 2018
@brendankenny brendankenny deleted the auditlistdisplay2 branch May 4, 2018 18:57
kdzwinel pushed a commit to kdzwinel/lighthouse that referenced this pull request Aug 16, 2018
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.

5 participants