New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autoprefixer processing comment to locally turn off grid polyfill continues to report IE related warnings #1333
Comments
Thanks for the issue. Do you want to send a pull request to save your name in the project history? You will need to add |
@ai |
I will be able to fix it only after a few weeks. Too much work too. |
When it rains it pours, right? ;) Anyway; the current work-arounds I have will hold for the short term, so a few weeks is fine. If for some reason I find the time to work on it sooner, can I notify you through this issue? |
I am preparing PostCSS 8 right now. This release could take 2-4 weeks. |
…grid warning (#1334) * Fix #1333 - /* autoprefixer grid: off */ will not output grid warnings * Adding test for #1333 (preventing warnings when grid is turned off) * Adding "npx" to "gulp play" command in playground CSS comment Not everyone has Gulp installed globally. This prevents people who don't have Gulp installed globally getting confused why "gulp play" doesn't work. * Triggering a warning if "subgrid" is used for any CSS value IE does not support subgrid and Autoprefixer can't polyfill subgrid either. * Updating tests to include subgrid warning Co-authored-by: Daniel Tonon <dan503.npm@gmail.com>
The fix was released in 9.8.5. |
Given the following snippit of CSS
Even though it is using the
/* autoprefixer grid: off */
processing comment, this particular block continues to raise a warning that "IE does not support justify-content on grid containers
." when conditionally applying grid styling.Elevating the processing comment to the scope of the
@supports
block itself yields the same result. It continues to report warnings related to IE's grid implementation. Only using/* autoprefixer: off */
in these places works as expected.While that suffices in the current situation for my problem, it is highly non-desired that the entirety of Autoprefixer has to be turned off. This would start causing problems once these rules end up containing properties which do need prefixing, requiring that e.g. an artificially split CSS rule be maintained where autoprefixer can still be turned off.
Autoprefixer version : 9.8.4
The text was updated successfully, but these errors were encountered: