Autoprefixer issues warning on fill-available in SCSS file (v4.0.1)
See original GitHub issueHi,
I’m compiling the scss file using webpack and the autoprefixer issues a warning on line 40:
max-height: -webkit-fill-available;
I noticed that you did change the fill-available to stretch on version 4.0.1 but I guess that autoprefixer doesn’t care that it’s already prefixed properly.
Since you’re also using webpack to compile the project, any reason why you’re not letting it autoprefix the final css? If we remove the prefixed line in the scss file, autoprefixer does its job and doesn’t complain anymore.
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
client/node_modules/autoprefixer/CHANGELOG.md - GitLab
This is a project which main goal is to develop a layout UI for experiment building that later on can be deployed in...
Read more >react-bootstrap autoprefixer warning - Stack Overflow
This is behaviour from Autoprefixer. I am not sure if this is a bug or feature, but I know that Autoprefixer 10.4.5 does...
Read more >CHANGELOG.md
Add note about `grid` option for grid properties in `autoprefixer --info`. ... 8.5.1 * Remove unnecessary warning on `-webkit-fill-available`.
Read more >10.3.1 - autoprefixer - npm
Parse CSS and add vendor prefixes to CSS rules using values from the ... warning API to warn about really important problems in...
Read more >A Guide To CSS Debugging - Smashing Magazine
Debugging in CSS means figuring out what might be the problem when you have unexpected layout results. We'll look at a few categories...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I hit this same issue but worked around it by putting
before my @import. Maybe this is causing problems I don’t notice, but things seem to work fine.
Released in 4.0.2