Closed coltborg closed 3 years ago
This closes #287.
When running rake assets:package, the CSS assets aren't run through a vendor autoprefixer, as happens automatically in a Rails app with the autoprefixer-rails gem.
rake assets:package
autoprefixer-rails
Calling autoprefixer manually in Ruby is able to vendor prefix the CSS that gets pushed to the /dist folder.
/dist
Automatically adding vendor prefixes adding better CSS support for older browsers.
In the Percy issues, Firefox v73.0 CSS needed an old -moz- prefix for appearance so that a <select> element can be customized.
v73.0
-moz-
appearance
<select>
After running rake assets:package, the outputted CSS (both .css and .min.css) should have -moz- -webkit vendor prefixes.
.css
.min.css
-webkit
For example:
Before
After
This closes #287.
What does this PR do?
When running
rake assets:package, the CSS assets aren't run through a vendor autoprefixer, as happens automatically in a Rails app with theautoprefixer-railsgem.Calling autoprefixer manually in Ruby is able to vendor prefix the CSS that gets pushed to the
/distfolder.Why does this matter?
Automatically adding vendor prefixes adding better CSS support for older browsers.
In the Percy issues, Firefox
v73.0CSS needed an old-moz-prefix forappearanceso that a<select>element can be customized.How to test this?
After running
rake assets:package, the outputted CSS (both.cssand.min.css) should have-moz--webkitvendor prefixes.For example:
Before
After