Closed kinday closed 8 years ago
We can add more than one rule to handle this situation
Example
a {
font: normal normal normal normal 100% normal normal; /* Browser applies this rule*/
font: normal normal normal normal medium/normal normal normal; /* Browser can`t parse this rule, so it uses previous */
}
@kinday What do You this about this solution?
I like how this solution takes best from my proposals yet remains simple.
@kinday After some research, I decided not to use a shortcut for font declaration. For 'text-decoration' we can use more short definition. U can see changes in the new release.
@maximkoretskiy, great job! I personally don’t use shorthands most of the time. The rule is not to use shorthand unless you set all the properties it covers.
Thank you. I think issue may be closed.
Thank you for feedback!
Easy way: don’t include attributes that are not supported widely into shorthands. Hard way: build fallback according to specified list of browsers using
caniuse
asautoprefixer
do.Example of Chrome completely ignoring![image](https://cloud.githubusercontent.com/assets/1751980/12218178/d094eb2e-b728-11e5-98c8-b905cf029e21.png)
font
shorthand: