Aggressive Degradation
It's worth noting that this is a personal opinion, and best suited to very specific situations. The stance of aggressive degradation will not be well received in large commercial projects or enterprise solutions relying upon older browsers.
Aggressive degradation dictates that if a particular (older) browser cannot render a certain effect, it should simply be omitted. A CSS3 button is a good example. Effects such as
border-radius
,box-shadow
,text-shadow
andgradients
will be displayed in cutting edge browsers. A graceful fallback of a.PNG
would be provided for slightly older browsers, and the most graceful of all solutions would include a PNG-Fix for IE6 or the use offilter
arguments to replicate gradients and shadows. However, aggressive degradation in this situation instructs you to neglect the older browsers and present them with a flat, satisfactory object.Put simply, aggressive degradation boils down to: if your browser can't render a gradient or a box shadow, tough luck.
While not ideal for every situation, it ensures the timely delivery of projects and that the root product is still usable and not reliant on (validation breaking) hacks.
Monday, August 1, 2011
Front End Development Guidelines - Great Read
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment