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
When using rem, a common way to add support for IE8 is with a px fallback:
.example {
font-size:24px; /* Fallback for IE8 */font-size:1.5rem;
padding:32px16px; /* Fallback for IE8 */padding:2rem1rem;
}
The clean-css advanced optimizations are removing the fallback, even when compatibility is on. It would be great if compatibility mode could detect and preserve px fallbacks.
@ademarre this is due to a fact not all properties have advanced optimisations implemented. This is due in version 2.4 with #290. So far please use your workaround or a --skip-aggressive-merging switch.
PS) #186 addressed basic optimisations not advanced ones so not such easy fix this time.
When using
rem
, a common way to add support for IE8 is with apx
fallback:The clean-css advanced optimizations are removing the fallback, even when
compatibility
is on. It would be great if compatibility mode could detect and preservepx
fallbacks.My current automated solution is to run robwierzbowski/node-pixrem after clean-css in my build. (See gruntjs/grunt-contrib-cssmin#112 (comment))
#186 addressed a related edge case.
The text was updated successfully, but these errors were encountered: