Skip to content

report(psi): remove redundant varience disclaimer#6110

Merged
paulirish merged 2 commits into
masterfrom
mayvarynothx
Sep 26, 2018
Merged

report(psi): remove redundant varience disclaimer#6110
paulirish merged 2 commits into
masterfrom
mayvarynothx

Conversation

@paulirish

Copy link
Copy Markdown
Member

Right now, "Values are estimated and may vary" is shown twice in the PSI case.

image

estValuesEl.textContent = Util.UIStrings.varianceDisclaimer;

// 'Values are estimated and may vary' is used as the category description for PSI
if (environment !== 'PSI') {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Is this being covered by tsc right now? :)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@patrickhulce whatcha mean

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

meaning is the magic string 'PSI' being checked to make sure we're using it correctly vs. psi, typo PS1 etc

@exterkamp

Copy link
Copy Markdown
Member

Would it make more sense to have it removed from the category descriptor so that it is more consistent across environments?

@patrickhulce patrickhulce left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

cool beans 👍

though I'd also wonder why not hide it with CSS on PSI side since we've got a clear classname for it :)

@paulirish

Copy link
Copy Markdown
Member Author

@exterkamp perhaps. but in this case it's a little different. for LS, we have field data at the top and this disclaimer doesnt apply. and then we have the category description that says "hi all this lab data is from lighthouse. it's different data so here's the disclaimer."

whereas in typical LH, we dont have a category description right now. but when we add one, it could make sense to move this disclaimer there.

@patrickhulce sure yeah. we could but so far we've avoided hiding with CSS and building the DOM how we want to use it.

@paulirish paulirish merged commit a097a23 into master Sep 26, 2018
@paulirish paulirish deleted the mayvarynothx branch September 26, 2018 19:03
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.

3 participants