10.4.13 onwards - not using vendor prefix when Electron needs it? about autoprefixer HOT 4 CLOSED

Downgrade to 10.4.12

Nope. It will not have since you already updated caniuse-lite and electron-to-chromium.

With new browsers database any Autoprefixer will do the same.

What would be the best approach?

You should the power of Browserslist config and define your requirements there (and then all tools will know that you need to support Electron 22.3.27, and new developers will know where to look).

Create .browserslistrc with, for instance, content:

Electron >=22.3.27

You can find what queries you have to define your target browser policies here: https://browsersl.ist/

Also that website can be useful to debug your Browserslist config: https://browsersl.ist/#q=Electron+%3E%3D22.3.27

from autoprefixer.

Hi. Very likely that Autoprefixer update triggers caniuse-lite and electron-to-chromium update and new version is not require -webkit-.

As we can see Chrome ≥120 doesn’t need -webkit- for masks https://caniuse.com/css-masks

And Electron ≥28 uses Chromium ≥120 and should work without -webkit- https://github.com/Kilian/electron-to-chromium/blob/master/versions.js#L145-L150

What Electron do you use to test?

from autoprefixer.

That makes sense, thank you. It's Electron 22.3.27 - we're currently bound to that version due to other dependency requirements. What would be the best approach? Downgrade to 10.4.12 until we can get Electron to 28?

from autoprefixer.

Thank you very much for your help - will do that.

from autoprefixer.