Css3 can i use

Check out css3pie. Not bad meaning bad, to quote NWA, but bad meaning good. Show 1 more comment. Active Oldest Votes. Not natively. Improve this answer. Hristo: Depending on which style you need. I didn't have any particular in mind I just know that IE sucks when it comes to cross-browser compatibility and I was wondering if WebKit was a way to fix that issue. Chrome dev's have forked webkit, and opera isn't using presto any longer — Richard.

EdgeHTML has now been discontinued also. Add a comment. So would the different rendering engines ignore these prefixes? JKirchartz is correct. The others browsers will ignore each others css-prefix. Nick Craver Nick Craver k gold badges silver badges bronze badges. So can -webkit- be used in like Firefox for advanced rendering of CSS3 features? No, Firefox uses a rendering engine called Gecko — Gareth.

Hristo - Firefox uses some similar properties but they're called -moz for mozilla , it'll ignore -webkit roles when parsing styles : — Nick Craver. CodeExpress CodeExpress 2, 1 1 gold badge 19 19 silver badges 16 16 bronze badges. Visit the link above, its informative and final climax is hilarious.

Sunil Garg Tycholiz Tycholiz 1 1 gold badge 13 13 silver badges 31 31 bronze badges. Update Chrome Frame is no longer maintained or supported…. Chrome Frame is no longer supported. It was a stop-gap solution at best. Navbar Vertical Navbar Horizontal Navbar. Shadow Effects Box Shadow.

Example a. Here I am! Exercise: Set the background-color to red, when you mouse over a link. Report Error. This process usually involves a lot of give and take with the web development community, standards organizations like W3C , and browser developers.

Newer properties often exist for some time before they can be reliably used on production sites. This happens for various reasons:. To allow use of a CSS specification that is not fully implemented in a browser or in early implementation, we use what are known as CSS Vendor Prefixes. Up until now, most of the CSS you've learned is fully supported in all browsers. For newer properties, from CSS3 and later, that's not always going to be the case.

One contributing factor that has to be considered, is perhaps that we are being held back out of fear. This might be a fear of trying something new, now that we have gotten so comfortable waiting for that magic day of compatibility to come. This fear could also stem from not wanting to stand up to some particular clients and try to make them understand this truism of the Web and the concessions that need to be made — with regards to consistent presentation across the browsers.

We get intimated, so to speak, into playing along with these unrealistic expectations, rather than trusting that we can make them see the truth of the situation. Whatever the cause is that drives this factor, we need to face our fears and move on.

A possible contributing factor that we should also look into is that some people in the community are just too comfortable with how we design today and are not willing to learn new technology. There are those of us who already tire of the extra work involved in the testing and coding to make everything work as it is, so we have little to no interest at all in an approach that seemingly calls for more thought and time.

But really, if we start using new technologies today, we will have to master a learning curve first, but the advantages are certainly worth our efforts. We should see it as the challenge that will save us time and deliver better and cleaner code. To some extent, today we are in the situation in which we were in the beginning of s; at those times when the emergence and growing support of CSS in browsers made many developers question their approach to designing web sites with tables.

Doubt is another thing we must consider when it comes to our being in hold mode, and this could be a major contributor to this issue. We begin to doubt ourselves and our ability to pull off this innovative, boundary pushing-kind-of-work, or to master these new techniques and specs, so we sink into the comfort of playing the waiting game and playing it safe with our designs and code.

We just accept the limitations and quietly work around them, railing on against the various vendors and the W3C. Faith can be a good thing, but in this case, it can hold you back. Image by fotologic. Undoubtedly, some of us are holding off on moving forward into these new areas because we are faithfully clinging to the belief that the cross-browser support push will eventually happen.

There are those saying that we will be better off as a community if we allowed the Web to evolve, and that this evolution should not be forced.

But this is not forcing evolution, it is just evolution. It is a gradual change over time. And that is what we should be allowing to happen with the Web, gradually using and implementing features for Web community here and there. This way forward progress is happening, and nobody should be held back from these evolutionary steps until we all can take them. Some members of the online community faithfully fear that if they go ahead and accept this new way forward and begin designing or developing in accordance, then as soon as they begin completing projects, the support might be dropped and they would need to update the projects they already completed in the past.

The widely accepted features are safe to use and they will not disappear for certain; the experimental features can always be extracted in a separate stylesheet and be easily updated and maintained when necessary. It might be a good idea not to use experimental, unsupported features in large corporate designs unless they are not affecting the critical design elements of the design.

We cannot forget to mention that there are also many of us who are refusing to dabble in these new waters simply due to the fact that implementing some of these techniques or styles would cause a plethora of vendor-specific pefixes to appear in the stylesheet, thus impeding the validation we as professionals strive for.

Many of us would never put forth any project that does not fully validate with the W3C, and until these new specs are fully standardized and valid, we are unwilling to include them in their work. Well, not quite. It neither contributes to accessibility, nor points out best-practices.