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
latest version of caniuse break current test #19
Comments
I will change the way i test compat. For now it depends too much on fixed data. What i really need to test, is that i have to take data from raw files, transform it, and test if the output is correct. I will automatize that soon. But for now, yes, just look at real data, it will be enough. Thanks ✨ |
I've added a workaround in 5e117df to prevent issue for now :). |
Ok, i see, well, it works for now. Both of the browsers do not have the same rendering engine, so the both of them have to be tested. |
My point is that caniuse-db is just keeping one entry for those browsers. That's the weird part. Eg: Fyrd/caniuse@41bd4f0 |
The diff for border-radius get support test now have a difference for
safari: { '#1': 6.1, x: 4, y: 3.1 }
.Note the
#1
added. I take a quick look into recent caniuse db update and saw this diff Fyrd/caniuse@44dc9c2Do you just want me to add this for the test ?
Maybe we should make test simpler (no deep equal) and just test keys to avoid testing data (we don't need to test data right?)
The text was updated successfully, but these errors were encountered: