Requirments:

1. Doesn’t use CSS3, too soon
2. Doesn’t use javascript unless it’s jquery. This is because maintaining more than one Javascript library starts to become a headache to keep track of. Jquery solves that problem because it is lightweight and can incorporate plugins to it’s core. Continuing to add plugins, however, eventually starts to detract from the value of having a lightweight library. This means heavier pages and more time looking around for plugins and dealing with any issues related to the plugin. In addition, you are using something that you may not be able to modify, debug or alter on your own. You thus have a dependency on a product that may eventually no longer be supported.
3. Same goes for using an additional PHP library, more stuff to maintain.
4. As little use of images as possible. This roundup is limited to solutions that use one image or less, there is already a wide selection of
   solutions that use 1 or more images. This is because changes to the design will require re-doing the image color size, background or all of them.
5. Something that can be called as a class. This means not having to declare a unique instance of that rounded corner for each time it will be implemented
6. Useable on as many browsers as possible. Degrades when not useable
7. A few lines of code as possible
8. Learn to accept that IE can’t have rounded corners. There are solutions available but they cost time and effort. Rounded corners are a web2.0 thing, anyone web savvy is using firefox at the moment.

1. One line of code to get rounded corners, simple and elegant. Displays the rounded corner in Firefox, but degrades well.
   
   
2. 
   
3. 
   
4. 
   
5. 
   
6. 
   
   
   
7. 
   
8. 
   
9. 
   
10. 
    
11. 
    
12. 
    
13. 
    
14. 
    

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.