Internet Explorer only saw an uptick in 2011. I have excluded Chrome for Android because of insufficient data.įrom 2007 until 2011, there was a steady increase in the numbers of prefixed features in all browsers. You can see the trend of the implementation of prefixed features across the major browsers in the chart above. I did some analysis on the caniuse dataset and Mozilla Developer Network Compat dataset to answer this question. It appeared that the problems created by vendor prefixes would fade away in time. Developers responded by making tools to automate the problem away.īrowser vendors slowly began to move away from prefixing, favoring feature flags inside the browser settings instead. It led to partial implementations of CSS features, introduced bugs, and ultimately created a fracture in the browser ecosystem, which disgruntled developers.
The number of prefixes grew, and with it, things grew confusing. In CSS we use vendor prefixes for properties, values, that are: – vendor specific extensions (per CSS 2.1), or – experimental implementations (per CSS Snapshot 2010) (e.g. It was seen as a way to implement non-standard features and offer previews of new standard features.īy 2012, the W3C CSS Working Group was issuing guidance on the use of vendor prefixes:
The raison d’être of prefixes was to specify browser-specific features. What is clear, is that by 2006, prefixed features were in Internet Explorer and Firefox. It‘s not clear who started prefixing, or when it began exactly. Let‘s take a quick stroll down memory-lane to revisit how vendor prefixing CSS properties came to be.
0 kommentar(er)
