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
If a browser doesn’t recognize a property or its corresponding value, the browser will ignore the property altogether. When this happens, the browser uses (or falls back) to the previous value it finds.
This is the easiest way to provide a fallback. Here’s an example:
.layout {
display: block;
display: grid;
}
In this example, browsers that support CSS Grid will use display: grid. Browser doesn’t support CSS Grid will fall back to display: block.
Maybe not a big deal with evergreen browsers as it used to be with IE 11 which we do not support.
But there are still cases, like overflow-overlay where the fallback values still make sense.
https://zellwk.com/blog/older-browsers-css/
As we use objects to declare styles we can't simply do:
We can use the similar approach as
fela-plugin-fallback-value
with arrays or something else.The approach to fallback values should be tested and documented.
The text was updated successfully, but these errors were encountered: