I know some of them and I wanted to ask you if you know any other prefixes than this ones
-moz
-webkit
-o
-khtml
Thank you for any help
I know some of them and I wanted to ask you if you know any other prefixes than this ones
-moz
-webkit
-o
-khtml
Thank you for any help
started this thread by listing several vendor prefixes and pointed out the Internet Explorer case. Instead of hand-maintaining multiple prefixed rules, the practical, modern approach is to write standard CSS and let a build tool add only the prefixes required for the browsers you target.
Use Autoprefixer (a PostCSS plugin) together with a Browserslist configuration so prefixes are added automatically at build time. Example quick steps:
Install and run the PostCSS CLI with Autoprefixer:
npm install --save-dev postcss postcss-cli autoprefixer
npx postcss src/styles.css --use autoprefixer -o dist/styles.css A minimal PostCSS config and a browserslist entry:
/* postcss.config.js */
module.exports = {
plugins: [
require('autoprefixer')
]
}
/* package.json (partial) */
"browserslist": [
"defaults",
"not dead",
"> 0.2%"
] Autoprefixer uses Browserslist to decide which prefixes to add. Check specific property support before changing targets — use caniuse to see browser compatibility and MDN for authoritative docs. Autoprefixer will not polyfill missing features (it adds only vendor-prefixed declarations), so for very old browsers you may still need fallbacks, feature detection, or polyfills. Keep the source CSS clean (no manual prefixes), run cross-browser tests for your selected targets, and update Browserslist as your support policy evolves.
References: Autoprefixer, Browserslist, Can I use, MDN — Vendor prefix.
Jump to Post— JorgeM 958Also, Internet Explorer: -ms-
Also, Internet Explorer: -ms-
Thank you
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.