Gavin McFarland

I'm getting an `invalid PostCSS plugin` using webpack. Maybe this is related?

I'm closing this for now, as empty properties are needed for the polyfill to work. People can try the suggestion above to see if it resolves the issue.

I know it's been a long time since you raised this issue, but this bug should be solved in the latest release.

Hi @frugan-it. Hmm, this is an odd one. I can't recreate the issue when I create an example repo with `webpack` and `postcss-loader`. This is my `webpack.config.js` file: ```js module.exports...

Thank you! I'll check it out and do some investigating.

So, I've looked into it a bit more. There is a conflict between `sass-loader` and a dependency my plugin uses called `postcss-values-parser`. `sass-loader` is removing the spaces between `attr(width) /...

I can probably also release a fix by adding some logic to avoid reading the values like the ones in the `aspect-ratio` prop as it doesn't need to.

No worries. I initially never saw the need to ignore certain rules, but I remembered the plugin ignores rules it's already processed, which have a comment of `* added by...

I know you created this issue a while ago but I'm just updating this issue. It should be fixed now because flex-gap-polyfill no longer looks at values in properties such...

Hi @Muluk-m. I think what is happening is `max-content` somewhere in your project and this is being combined with something in the polyfill. Since `max-content` can't be computed by CSS...