Style Sheets vs. Frames as Web Extensions
Posted By Faye
Date: February 10th, 2010
Category: innovation
In considering how to extend the Web with new technologies, it is instructive to compare Cascading Style Sheets (CSS) with frames. CSS is an elegantly designed extension, whereas frames suck, as I have said many times CSS is backward compatibleto the extent that viewing a style-enhanced site with an older browser causes no problems at all. Of course, the user doesn’t see the stylistic enhancements made possible by CSS (e.g., multiple fonts and indented margins), but the text of the page will be readable and will be presented in a reasonable default style (of course, the extent to which you deem the default presentation reasonable depends on your assessment of the quality of typography in mainstream browsers: admittedly rather poor). In contrast, a page designed with frames is useless for a user with an old browser.CSS isorthogonal to other featuresin Web browsing. When multiple style sheets become supported in future releases of the mainstream browsers, users might want to learn the command to switch between styles, but they won’t have to. Even if users do learn this new command, it will not interfere with or change their understanding of earlier commands and operations. In contrast, frames destroy bookmarks, change the meaning of established commands like “print” and “view source”, and in general make a mess of the user’s prior understanding of the Web. CSS builds on the philosophy of the Web: cross-platform design and simple-to-understand codes that are precisely documented in public specifications. In contrast, frames are hard to learn for authors, poorly documented, and have no chance of working on anything except desktop computers with relatively large screens (try fitting frames on a Pilot palmtop and you will see what I mean).Read more in http://www.useit.com/alertbox/styles_vs_frames.html