Treehouse: Grow your CSS skills. Land your dream job.

Property without prefixes

  • # June 3, 2013 at 7:59 am

    Hi, guys.
    I can’t find a list of properties which I have to use with prefixes, maybe somebody can share. Thanks in advance.

    # June 3, 2013 at 8:03 am

    # June 3, 2013 at 8:05 am

    Major prefixes:

    -webkit- Safari, Chrome (and other WebKit-based browsers)
    -moz- Mozilla Foundation (Gecko-based browsers)
    -ms- Microsoft
    -o-, -xv- Opera Software

    Minor prefixes:

    mso- Microsoft Office
    -atsc- Advanced Television Standards Committee
    -wap- The WAP Forum
    -khtml- Konqueror browser
    -apple- Webkit supports properties using the -apple- prefixes as well
    prince- YesLogic
    -ah- Antenna House
    -hp- Hewlett Packard
    -ro- Real Objects
    -rim- Research In Motion
    -tc- Tall Components

    Reference: StackOverflow. I would dabble into what Paulie_D said since it is the W3C.

    # June 3, 2013 at 8:07 am

    # June 3, 2013 at 8:11 am

    # June 3, 2013 at 8:16 am

    > -webkit- Safari, **Chrome** (and other WebKit-based browsers)

    Not anymore. Chrome is running on Blink now.

    > -o-, -xv- Opera Software

    Same here. Opera is running on Blink.

    # June 3, 2013 at 8:20 am

    >Not anymore. Chrome is running on Blink now.

    Which is a webkit it will still apply.

    >Same here. Opera is running on Blink.

    Not the older versions.

    # June 3, 2013 at 8:23 am

    Wow, so fast. Thanks.

    # June 3, 2013 at 8:23 am

    @HugoGiraudel, Awesome! So is it safe to say we can drop -webkit- and -0- now?

    Thanks for sharing that, I didn’t even know about Blink. Did they publish that already?

    @Paulie_D Is -webkit- primarily used for older browser versions than?

    # June 3, 2013 at 8:25 am

    Canary is using Blink right now.

    >So is it safe to say we can drop -webkit- and -0- now

    Absolutely NOT….unless you are dropping support for anything other than the latest browser versions.

    Even then, Blink is still a WK fork so I would expect the prefix to still apply for **experimental** features in..erm..Blink

    # June 3, 2013 at 8:27 am

    Hold on:


    >**Vendor Prefixes**

    >Historically, browsers have relied on vendor prefixes (e.g., -webkit-feature) to ship experimental features to web developers. This approach can be harmful to compatibility because web content comes to rely upon these vendor-prefixed names. Going forward, instead of enabling a feature by default with a vendor prefix, we will instead keep the (unprefixed) feature behind the “enable experimental web platform features” flag in about:flags until the feature is ready to be enabled by default. Mozilla has already embarked on a similar policy and the W3C CSS WG formed a rough consensus around a complementary policy.

    # June 3, 2013 at 8:29 am

    @Paulie_D I guess my excitement for tossing vendor prefixes made me jump the gun. Thanks for clarifying. Hell, i still use -webkit- for box-shadow for Android 2.0 and below development.

    # June 3, 2013 at 9:08 am

    I dropped old webkit syntax for gradients because I think it’s too much effort and weight for basically just a few % people that can’t (be bothered to) upgrade to Android 4.0+ :P

    I don’t like the experimental flag, doubt anyone other then developers will enable that so what’s the point?

    Another option: no prefixes and still list standardized syntax last, read (I think it’s sort of off-topic but with css3please and caniuse this topic is solved anyway)

    # June 3, 2013 at 10:03 am


    I feel that, more often than not, a JS solution such as “prefix-free” is the answer.

    # June 3, 2013 at 10:42 am

    Well, Blink won’t be around until Chrome 28, which is still far from stable/release.

Viewing 15 posts - 1 through 15 (of 18 total)

You must be logged in to reply to this topic.