Adobe Flex Authors: Matthew Lobas, PR.com Newswire, Shelly Palmer, Kevin Benedict

Related Topics: Adobe Flex

Adobe Flex: Article

Why Use CSS?

The benefits offer the best reason

Since the launch of Dreamweaver MX 2004, I've had numerous opportunities to demonstrate its new features and power to both new and existing Dreamweaver users. As with any product demonstration, it doesn't take long before I'm singing the praises of Dreamweaver MX 2004's abilities to design and render CSS, or Cascading Style Sheets.

Recently, however, a novice user asked a question, which, quite honestly, startled me. The user simply asked, "Why should I use CSS?" I realized at that moment that while those of us who work with HTML and CSS on a daily basis are intimately familiar with the benefits, many of you are not.

CSS Beginnings
The governing body of the Web, the W3C, recommended the use of CSS in December 1996 with the ratification of the CSS Level 1 specification, which described attributes for use in HTML pages. These attributes replaced the traditional font tag and other "style" markup such as color and margins. In May 1998, the W3C ratified CSS Level 2, which introduced positioning attributes. These attributes replaced the rampant (and incorrect) usage of the table tag to design the presentation of page elements. The most recent revision to the CSS specifications is CSS 2.1, which refines some attributes and removes others that had only limited, if any, usages in current browsers.

Unfortunately, CSS has been slow in reaching broad adoption. One of the key reasons for this was the browsers, and, in turn, the Web designers building sites for these browsers. At the time of CSS ratification, Netscape Navigator was still the dominant browser, and its support for CSS was basically nonexistent. Microsoft added very limited support with version 3 of its browser, but most Web designers at the time (this author included) were still coding their pages with Netscape as their reference platform.

Over the years, with each new version, the browser makers have expanded their support of CSS. Today, Internet Explorer 6, Netscape Navigator 7, Mozilla, Opera, and Safari all fully support CSS. That's not to say that our lives as Web designers and developers are without problems. While the above-mentioned browsers support CSS Level 2, they do so with varying degrees of compliance. In some cases, certain attributes still give you cause for frustration. In other words, you still need to follow the age-old mantra of "test, and test often." However, if you stick to core attributes of the CSS specifications, your pages will render correctly.

But why did the W3C create the CSS specification at all? What does it all mean to me as I create HTML-based Web sites and applications? In my opinion, you can divide up the need for CSS and its resulting benefits into three main areas: flexibility, rendering, and accessibility.

I'm sure that almost every Web designer and developer has experienced that moment of panic when, after meticulously laying out a page - complete with numerous nested tables - the client requests a "small" change. This could be something as simple as "can you move that image a little to the left," or as dramatic as "I'm not happy with those headers, can you make their font larger - and while you're at it, how about changing their color too?" If you're dealing with a limited number of pages, you can take a deep breath and spend the better part of an hour making those irritating changes. But when you're dealing with the larger sites, which have become the norm, a simple change is suddenly anything but simple.

What causes the panic in these situations? The markup, which defines the appearance of our pages, is actually part of the pages themselves. To see an illustration, take any given page from one of your sites and count the number of font and table tags. If only you could remove this markup from the flow, or code, of the actual page - and, even better, if you could externalize it -you could make the changes in a centralized place. Sounds like a job for CSS.

By designing your pages using a single, or even multiple, external style sheets, you can apply those changes to your site by modifying the style sheet and uploading the modified version.

Imagine how difficult it would be to move your site navigation from the left side of the page to the right in a traditional table-based layout. This would take hours of repetitive and very tedious work. If, however, you used the positioning attributes of CSS (more commonly known as CSS-P) to design your pages, a simple change to the "float" attribute in the external style sheet would update the page. There's also an added benefit: you've updated every page that uses that style sheet on the site!

Since broadband has become mainstream, many developers have stopped considering how much time it takes to render a page in a browser. However, for many of you it's important to remember that your target audiences still surf the Web on dial-up connections. The traditional table-based layout is one of the primary causes of slow-loading pages. This happens because the browser, upon receiving the page from the server, must first examine and "understand" the complex array of nested tables. It must first locate the most deeply nested piece of content and then meticulously work its way back out of the code until it reaches the uppermost container, the body tag. Only after completing this journey can the browser begin rendering the content on the screen.

When you use CSS, the browser begins the rendering process as soon as it receives the content from the server because there is little, if any, actual presentational markup in the page.

There is also a hidden rendering benefit when using external style sheets. In the traditional table-based approach, the browsers must retrieve, analyze, and render each page individually. In other words, the browser is working just as hard at displaying the 30th page in your site as it was when displaying the first page.

If, however, the site uses external style sheets for its presentation, the first page prompts the browser to cache the linked style sheet files that the page uses. This means that all of the subsequent pages in the site using those style sheets will load even faster, since the browser has already cached the style sheets.

The final rendering benefit reminds me of the movie Amadeus. In the movie, Mozart asks the emperor what he thought of one of his operas. The emperor responds that it was good, but tedious. When pressed by Mozart, the emperor explains that the problem was simply that there were "too many notes." With Web design, this can also be a problem - the notes are the actual HTML code. The more code there is, the longer it takes the browser to understand and make sense of the page.

When you implement CSS in your designs, you decrease the amount of code the client needs to download. Simply removing all of the font tags from some pages can minimize the amount of code dramatically. If you move to completely CSS-P designs, in many cases you can minimize the amount of code by 50% or more! Less code equals faster-loading pages.

I hear a lot about accessibility these days. Most developers know that they should be thinking about building more accessible sites, but to a large degree only those developers who build sites for government or educational institutions have been forced into actually doing it. When thinking about accessibility, a majority of developers assume this means that they simply need to add things like alt attributes to their images. But there is actually much more to accessibility, and using CSS can make it easier for you to build accessible sites.

One of the primary issues of accessibility - and one where CSS can really make a difference - is in how an assistive technology such as a screen reader "reads" a page. In the traditional table-based world, a screen reader faces an incredible challenge in deciding how to read a page. Think about how confusing it must be for a screen reader as it encounters a deeply nested table - should it read the content, or skip over it? And if it skips over it, how does it get back to the content later?

As you hit a page, you can quickly spot the content that interests you and ignore the navigation or other content at the top of the page. Visually impaired people don't have this luxury. They must wait for the screen reader to parse through all of the extraneous information between the top of the page and the content they are really interested in.

Of course, there are techniques to make the screen reader skip the navigation, but these usually require adding links to images in your navigation bar or other content. While these techniques work, they can also be confusing, and sighted visitors can see them as well. Using CSS, you can define completely invisible elements on the page - elements that are invisible to other site visitors and your mouse. The screen reader can use these elements to navigate quickly and effectively through the document.

With CSS and its lack of presentational markup, the only thing that a screen reader encounters is actual content. Additionally, as you design using CSS-P, you begin to concentrate on the actual "flow" of content and consider its logical order on the page.

As you've been reading this article you followed the "flow" of information. But in that nested table example, this paragraph could just as easily have been in the upper right-hand corner of the page. In that case, the screen reader would have no way of knowing that it should wait until the end of the article to read it.

Using CSS-P, the browser could display this paragraph in the upper right corner of the page, but its position in the actual text or flow of the document would still be right here where you are seeing it. This makes for a much better, more accessible experience.

.  .  .

There you have it. I hope I've explained some of the unique benefits of using CSS in your Web endeavors. Obviously, there's a lot to learn.

More Stories By Greg Rewis

Greg Rewis is chief Web technologies evangelist at Macromedia. It is Greg's responsibility to be a public spokesperson for the Macromedia Web publishing suite of software and Web application development servers - as well as to represent the company's customers in an advocate's role on the product development teams.

Comments (2) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

Most Recent Comments
Jon 05/20/04 01:16:44 PM EDT

I started using CSS way back in 98. I have been using and learning more about CSS ever since. One thing I wanted to add to your article, for the beginner, using CSS for text formatting is a great place to start. Creating a simple CSS file with all the selectors formatted, P,A,A:Hover,HR, H1, H2 etc. Even a few styles for tables is also a good starting place.(.myTD,.mainTable, etc.) Then after you have that down you will understand how the whole thing works when you move into CSS-P. I think learning to use CSS is worth the time it takes. My first CSS-P job was a multi-million dollar application GUI that had to be lite, and very flexible. The whole app runs off a handful of CSS files. The developers really liked how easy it was to adjust the pages.
Take care,

FOTG Design and Film

Jim Rommens 05/20/04 10:12:19 AM EDT

Thanks for the interesting and helpful notes on CSS and its benefits. I see they are more important than just using them for font attributes.

IoT & Smart Cities Stories
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
DXWordEXPO New York 2018, colocated with CloudEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
In an era of historic innovation fueled by unprecedented access to data and technology, the low cost and risk of entering new markets has leveled the playing field for business. Today, any ambitious innovator can easily introduce a new application or product that can reinvent business models and transform the client experience. In their Day 2 Keynote at 19th Cloud Expo, Mercer Rowe, IBM Vice President of Strategic Alliances, and Raejeanne Skillern, Intel Vice President of Data Center Group and G...
DXWorldEXPO LLC announced today that All in Mobile, a mobile app development company from Poland, will exhibit at the 22nd International CloudEXPO | DXWorldEXPO. All In Mobile is a mobile app development company from Poland. Since 2014, they maintain passion for developing mobile applications for enterprises and startups worldwide.
Founded in 2000, Chetu Inc. is a global provider of customized software development solutions and IT staff augmentation services for software technology providers. By providing clients with unparalleled niche technology expertise and industry experience, Chetu has become the premiere long-term, back-end software development partner for start-ups, SMBs, and Fortune 500 companies. Chetu is headquartered in Plantation, Florida, with thirteen offices throughout the U.S. and abroad.
DXWorldEXPO | CloudEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
The standardization of container runtimes and images has sparked the creation of an almost overwhelming number of new open source projects that build on and otherwise work with these specifications. Of course, there's Kubernetes, which orchestrates and manages collections of containers. It was one of the first and best-known examples of projects that make containers truly useful for production use. However, more recently, the container ecosystem has truly exploded. A service mesh like Istio addr...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
@DevOpsSummit at Cloud Expo, taking place November 12-13 in New York City, NY, is co-located with 22nd international CloudEXPO | first international DXWorldEXPO and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time t...
SYS-CON Events announced today that DatacenterDynamics has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.