Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

<button /> browser default buttonface created no diff in build

See original GitHub issue

Hi there, i have a problem with a browser default behavior. We had a tailwind css reset which contains button { background-color: transparent }. Which means our list item component should be white (transparent).

But due reasons we decided to remove this reset.

And now the bug is appearing!

The button gets the browser default background “backface” and the item gets grey:

The bug is, that the chromatic build didnt get a diff and stop the build. The same in the other direction, if i accept the buttonface grey, and add the transparent color back again. Chromatic didnt stop the build.

Grey buttonface browser default:

White background-color: transparent:

The snapshots are correct and a diff is clear visible. What can we do?

Did you need more?

cheers

Issue Analytics

State:
Created a year ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

codykaupcommented, Oct 19, 2022

Bummer! I was hoping the fix was going to be one of those settings but it seems like this may require more investigation. Would you mind using our in-app chat to keep this conversation going? It’s our preferred method of troubleshooting and it’s better for customer privacy. This repo is used for issues specific to the CLI but this is going to be deeper in Chromatic.

Thanks!

1reaction

codykaupcommented, Oct 17, 2022

Hey @dutscher! 👋

It appears those snapshots are just slightly under the default Chromatic threshold of .063. We have a public Storybook to test this out and I was able to trigger the diff at .060. If you change the threshold for that story, Chromatic should pick it up!

I hope this helps!