In the web development industry, every web developer (including me) tends to hold a special place for CSS3 in his or her heart. The reason? It is a great solution for creating the interactive effects, animations and nice-looking navigation menus. It comes with many interesting additions which mainly include multiple backgrounds, text-shadow, border-image, opacity, box-sizing, border-radius and lots more. It is great choice to get started with the process of website development.
Truly speaking, I am very inspired with the increased and widespread use CSS3. It is more useful than HTML5 in practical terms. It provides us a high level of flexibility when it comes to PSD to HTML, PSD to XHTML or PSD to HTML5 development. We all use CSS3 to style web pages written in markup languages – HTML, XHTML and HTML5. But, there are few things about CSS3 framework which frustrates me a lot. Let’s take a look:
1) Tags : One thing that many developers hate most about CSS3 is that it revolves around the sheer volume of new tags. It is very difficult to remember all tags, recall the values and learn all background gradient, border image options to convert PSD to CSS3 properly. And so you need to refer online manuals again and again to keep everything on right tracks.
2) Vendor prefixes : It is one thing which give a real pain to mainly developers. Truly speaking, I have a love-hate relationship with vendor prefixes. I personally don’t like them much because prefixes are not very developer-friendly. Moreover, it may result in clunky repetition. The worst part is that they oftentimes, use entirely dissimilar syntax. To overcome this issue, you need to use JavaScript and server-side pre-processors.
Rounded corners is something that I like most about CSS3. It has brought a lot of relief to many web developers and web designers. It helps to deal with complicated layouts or multiple background images. Unfortunately, it does not supports Internet Explorer 8 and therefore, professionals are left only with two possible options – (a) either say no to CSS3 and switch to the use traditional web development techniques or (b) simply accept that two web browsers can’t render similar results.
But, the question is how to deal with web pages that look uglier in IE8. Majority of web developers tend to take an advantage of JavaScript shims to make Internet Explorer 8 look better. This attempt to get pixel perfection results in a bulky set of codes which surely slow down the loading speed of a website. That’s why many developers just hate it.
0 comments:
Post a Comment