CSS厂商前缀是临时方案，还是可长期填补CSS标准兼容差距？

Great question—vendor prefixes (like -webkit-, -moz-, -ms-) have been a staple of cross-browser CSS for years, but their role is strictly temporary by design. Let’s break down your two questions clearly:

Are they just a temporary solution that becomes obsolete once old browsers are phased out? #

Absolutely. This is exactly why vendor prefixes exist in the first place. Here’s the breakdown:

• When a new CSS feature is still in draft (not fully finalized by the W3C), browser vendors add a prefix to their experimental implementation. This lets developers test the feature early, while protecting users from breaking changes if the standard gets revised.
• Once the feature’s spec is finalized, vendors will roll out support for the unprefixed, standard version of the property. Over time, as older browser versions (that only supported the prefixed version) get replaced or abandoned, the prefixes become unnecessary.
• For example: Early versions of Flexbox required -webkit-flex or -moz-flex, but today every modern browser supports the standard flex property. You’d only need the prefixed versions if you’re still supporting ancient browsers like IE10 or Firefox 28—something most projects don’t need to do anymore.

Can we still rely on them to fill compatibility gaps when new CSS versions are released? #

Sort of, but with big caveats:

• For draft-stage features: Vendors might still add prefixes for experimental support, but these are not meant for production. The prefixed implementation could change drastically (or even get dropped) if the spec evolves, so using them in live code is risky.
• For finalized but partially supported features: In the short term, prefixes can help cover browsers that haven’t yet rolled out the standard version. But this is still a temporary fix. Once those lagging browsers drop below your project’s supported threshold, you can ditch the prefixes.
• Pro tip: You almost never need to write prefixes manually anymore. Tools like autoprefixer automatically add (or remove) prefixes based on your target browser list, so you can write standard CSS and let the tool handle the compatibility legwork.

Bottom Line #

Vendor prefixes are transitional tools, not permanent solutions. They exist to bridge gaps between experimental feature testing and full standard support, or between old browsers and modern standards. As browsers update and specs stabilize, they’ll always be phased out in favor of the official, unprefixed CSS syntax.

内容的提问来源于stack exchange，提问作者Ayman Morsy