Consider toggling vendor prefixing on/off (stylis v3)

This is regarding 2.0.0-15.

Using flex boxes results in:

There is absolutely no reason to add these… and it is likely a performance hit (processing unknown CSS properties is just another cycle).

There is a boolean way to check whether a property is supported in the browser. See Verou’s article http://lea.verou.me/2009/02/check-if-a-css-property-is-supported/.

Possible performance issues aside, it is a nuisance from the DX perspective (as visible in the screenshot).

[callumlocke]

Just to point out, this problem is not just a matter of aesthetics. Unwanted prefixes are a footgun: if you click to disable a property in the devtools, the browser may quietly fall back to some prefixed property. If you fail to notice this, it can lead to minutes or hours of pointless layout debugging. And even when you do notice it, it’s painstaking to make sure you catch each potential fallback property and disable them all. It’s effectively not even worth using this feature of the devtools, as it’s easier to make the change in your code and wait for it to rebuild and then change it back again.

[bengotow]

Hey folks - just wanted to chime in regarding DX. I’m building an application that targets Electron (essentially I’m only building for the /very/ latest version of Chromium), and I’d really like if I could turn off all vendor prefixing. I don’t need it and it makes things look messy in the inspector, and harder to change at runtime (because removing a property causes Chrome to fall back to it’s second choice prefixed property.)