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(redesign): inline display text. bold audit header text #8592

Merged
merged 7 commits into from
May 3, 2019
Merged
15 changes: 12 additions & 3 deletions lighthouse-core/report/html/report-styles.css
Original file line number Diff line number Diff line change
Expand Up @@ -450,7 +450,6 @@
}


.lh-audit__title,
.lh-audit__display-text,
.lh-load-opportunity__sparkline,
.lh-chevron-container {
Expand All @@ -460,13 +459,23 @@
margin-right: 0;
}

.lh-audit__title {
.lh-audit__display-text {
flex: 1;
}

/* Prepend display text with em dash separator. But not in Opportunities. */
.lh-audit__display-text:not(:empty):before {
content: '—';
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
content: '';
content: '\2014';

Copy link
Member

Choose a reason for hiding this comment

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

can this just go in the HTML? Kind of weird to do it with a pseudo-element

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

why? dt encoding issues are resolved

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@brendankenny can't just be HTML, need some sort of logic check. makes sense to me to have the display + logic in one place here.

Copy link
Member

Choose a reason for hiding this comment

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

can't just be HTML, need some sort of logic check. makes sense to me to have the display + logic in one place here.

I don't think it needs to be. Opportunities and the rest of the audits share text with a .lh-audit__display-text class, but they actually come from different templates, #tmpl-lh-opportunity vs #tmpl-lh-audit. If the #tmpl-lh-audit template gets the em dash inline, then it'll only show up there

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good catch on the template thing. But would still need a length check - and can't make a CSS rule for preceding sibling (pseudo code below).

image

.lh-audit__separator {
  margin: 0 var(--audit-item-gap);
}
/* not actually a thing */
.lh-audit__display-text:not(:empty) - .lh-audit__separator {
  display: none;
}

Copy link
Member

Choose a reason for hiding this comment

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

per discussion in chat.. let's use whitespace on both sides of the dash.

Assuming we want to use var(--audit-item-gap) the we'll need some margin in here too:

  margin-right: var(--audit-item-gap);

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

margin-right: var(--audit-item-gap);
}
.lh-audit-group.lh-audit-group--load-opportunities .lh-audit__display-text:not(:empty):before {
display: none;
}

/* Expandable Details (Audit Groups, Audits) */
.lh-audit__header {
display: flex;
font-weight: 500;
padding: var(--lh-audit-vpadding) 0;
}

Expand Down Expand Up @@ -684,7 +693,6 @@

.lh-load-opportunity__col {
display: flex;
justify-content: space-between;
}

.lh-load-opportunity__col--one {
Expand Down Expand Up @@ -868,6 +876,7 @@
}
.lh-audit-group__header span.lh-audit-group__description::before {
content: '—';
margin: 0px var(--audit-item-gap);
}

.lh-clump > .lh-audit-group__header,
Expand Down