7

I could understand using them for experimental things that aren't official (ie; not in the CSS3 spec) to prevent name collisions, but why the need for prefixes on shadowing and such?

Shouldn't each vendor be implementing the effects the same, as per the CSS3 specs?

EDIT: Will the prefixes go away once CSS3 is finalized? I just am curious about the history of why some features have prefixes, and some don't, when the effect seems to be the same on all major browsers.

Parker
  • 8,539
  • 10
  • 69
  • 98
  • Youv'e heard of Micro$soft right? When have they EVER been standards compliant? – rws907 Nov 15 '13 at 06:24
  • @rsmith84 Null point. That doesn't explain why all the major browsers have prefixes for some CSS3 stuff. – Parker Nov 15 '13 at 06:34
  • dog and cat both are different..... ! but just the same is that they are animal – Bhojendra Rauniyar Nov 15 '13 at 06:36
  • 1
    @rsmith84: au contraire, the default position for recent-ish IEs has been "we don't implement things that are not a final standard yet", even if the chances are very slim they'll change again. – Ulrich Schwarz Nov 15 '13 at 06:37

2 Answers2

11

CSS specs are known to take ages to reach the Candidate Recommendation stage which is the stage where they are considered implementation-ready. And even then, a CR can bounce back to WD if problems are found during the implementation and testing stage (this was such a problem with CSS2 that it eventually became CSS2.1).

Since the industry demands fast developments in technology, vendors have to try and implement standards far before they reach maturity. These implementations are often considered experimental and non-final, which brings us back to what you said about them being used for experimental features.

Will the prefixes go away once CSS3 is finalized?

Originally prefixes went away once a module and its implementations were finalized (CSS3 itself is never finalized because it's always growing). These days, measures are being taken to eliminate the use of prefixes for developing technologies almost entirely because they were being misused by both vendors and authors and causing unforeseen but serious interoperability problems; see Chromium/Blink and this CSSWG blog post.

BoltClock
  • 700,868
  • 160
  • 1,392
  • 1,356
4

This has been asked before, but the short answer is that CSS3 is not a finished product. CSS 2.1 wasn't published until 2011, and only a handful of CSS3 modules have even reached the level of a formal recommendation, so it's premature to talk about a CSS3 specification that is universally implemented. Thankfully, modern browser makers are helping to push things forward and are helping to craft the standard which follows the lead of real-world practice. As they move closer to general standards, the prefixes are dropped.

Community
  • 1
  • 1
denmch
  • 1,446
  • 12
  • 20