You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
.foo {
background-image:linear-gradient(to right,#333,#CCC);
background-image:-webkit-radial-gradient(center center, circle contain, black 0%, blue 25%, green 40%, red 60%, purple 80%, white 100%);
background-image:-moz-radial-gradient(center center, circle contain, black 0%, blue 25%, green 40%, red 60%, purple 80%, white 100%);
background-image:radial-gradient(yellow, green);
background-image:repeating-linear-gradient(red, blue 20px, red 40px);
background-image:repeating-radial-gradient(red, blue 20px, red 40px);
}
Result:
Hover preview appears for the first three, but is blank (empty checkerboard). Hover preview does not appear for the last two.
Expected:
Should we be more consistent? It seems better to not show a preview for unsupported cases rather than to show a preview that's incorrect. But how hard is it to detect which cases are supported?
The text was updated successfully, but these errors were encountered:
Note: I'm going to disable some of the Hover Preview unit tests that depend on the answer to this. We should re-enable them once the expected result is decided.
Update unit tests to use this new, cleaner way of getting info.
Disabled some gradient unit tests where the provider is generating nonsensical
CSS, pending resolution of #3535.
Hover over each of the following:
Result:
Hover preview appears for the first three, but is blank (empty checkerboard). Hover preview does not appear for the last two.
Expected:
Should we be more consistent? It seems better to not show a preview for unsupported cases rather than to show a preview that's incorrect. But how hard is it to detect which cases are supported?
The text was updated successfully, but these errors were encountered: