CSS
ARTICLE SUBJECTS
being →
database →
ethics →
fiction →
history →
internet →
language →
linux →
logic →
method →
news →
policy →
purpose →
religion →
science →
software →
truth →
unix →
wiki →
ARTICLE TYPES
essay →
feed →
help →
system →
wiki →
ARTICLE ORIGINS
critical →
forked →
imported →
original →
index
CSS
Cascading Style Sheets (CSS) is a language that is used to describe the stylistic presentation of a structured document written in HTML or XML. The CSS specification is maintained by the World Wide Web Consortium (W3C).
Advantages of using CSS include:
CSS has a syntax that is relatively simpler than that of HTML, and uses a number of English keywords to specify the names of various style properties. Here is a simple example of what CSS code looks like:
Here, the HTML elements
The CSS descriptors given above can be included within the HTML document, or imported separately. This capability gives CSS much of its flexibility and power. Additionally, CSS can be used with XHTML, XML, or in fact any structured document format which is properly implemented in an associated user agent or browser.
As the HTML language grew, however, it came to encompass a wider variety of stylistic capabilities to meet the demands of web developers. With these capabilities, style sheets became less important, and an external language for the purposes of defining style attributes was not widely accepted until the development of CSS.
The concept of Cascading Style Sheets was originally proposed in by . was at the time working on a browser called Argo which used its own style sheets; the two decided to work together to develop CSS.
A number of other style sheet languages had already been proposed, but CSS was the first to incorporate the idea of “” -- the capability for a document’s style to be inherited from more than one “style sheet.” This permitted a user’s preferred style to override the site author’s specified style in some areas, while inheriting, or “cascading” the author’s style in other areas. The capability to cascade in this way permits both users and site authors added flexibility and control; it permitted a mixture of stylistic preferences.
HÃ¥kon’s proposal was presented at the “Mosaic and the Web” conference in in , and again with Bert Bos in . Around this time, the World Wide Web Consortium was being established; the W3C took an interest in the development of CSS, and organized a workshop toward that end. HÃ¥kon and Bert were the primary technical staff on the project, with additional members, including Thomas Reardon of Microsoft, participating as well. By the end of 1996, CSS was nearly ready to become official. The CSS level 1 Recommendation was published in December .
Early in , CSS was assigned its own working group within the W3C, chaired by . The group began tackling issues that had not been addressed with CSS level 1, resulting in the creation of CSS level 2, which was published as an official Recommendation in May . CSS level 3 is still under development as of .
Even the browsers that did achieve full implementation often did so with a degree of difficulty; many implementations of CSS are fraught with inconsistencies, bugs and other quirks. Authors have commonly had to utilize hacks and workarounds in order to obtain consistent results across browsers and platforms. One of the most well-known CSS bugs is the Internet Explorer box model bug; box widths are interpreted incorrectly in several versions of the browser, resulting in blocks which appear as expected in most browsers, but are too narrow when viewed in Internet Explorer. The bug can be avoided, but not without some cost in terms of functionality.
This is just one of hundreds of other CSS bugs that have been documented in various versions of Internet Explorer, Netscape, Mozilla, and Opera, many of which have severe detrimental effects on the legibility of the document; the proliferation of such bugs in CSS implementations has made it difficult for designers to achieve a consistent appearance across platforms. However, currently, Mozilla’s Gecko layout engine is the best at rendering CSS, while Internet Explorer remains the worst at rendering CSS by standards set down by World Wide Web Consortium.
For example, the HTML element
Customarily, headings are rendered in decreasing order of size, with
Prior to CSS, document authors who wanted to assign a specific color, font, size, or other characteristic to all
The additional presentational markup in the HTML made documents more complex, and generally more difficult to maintain; if all level two headings were to be rendered in this style, the markup had to be used for each one separately. Furthermore, a person reading the page with a web browser loses control over the display of the text; if they would rather see the heading in blue, they cannot easily do so, as the site author has explicitly defined the heading color to be used.
With CSS, the
With an accompanying style sheet to define the red italic style and white background:
Thus, presentation is separated from content. (It is because of the advantages offered by CSS that the W3C now considers many of the presentational elements and attributes in HTML to be deprecated). The HTML describes only structural aspects, and the CSS describes all presentational aspects. CSS can define color, font, text alignment, size, and also non-visual formatting such as the speed with which a page is read out loud in text readers.
CSS style information can be either attached as a separate document or embedded in the HTML document. Multiple style sheets can be imported, and alternative style sheets can be specified so that the user can choose between them. Different styles can be applied depending on what media is being used. For example, the screen version may be quite different from the printed version. This allows authors to tailor the presentation appropriately for each kind of media. Also, one of the goals of CSS is to allow users a greater degree of control over presentation; users who find the red italic headings difficult to read may apply their own style sheet to the document, and the presentational characteristics will be “cascaded”; the user may override just the red italic heading style, and the remaining attributes will stay the way they are.
The W3C maintains the CSS1 Recommendation.
CSS level 2 was developed by the W3C and published as a Recommendation in May . A superset of CSS1, CSS2 includes a number of new capabilities, among them the absolute, relative, and fixed positioning of elements, the concept of media types, support for aural style sheets and bidirectional text, and new font properties such as shadows. The W3C maintains the CSS2 Recommendation.
CSS level 3 is currently under development. The W3C maintains a CSS3 progress report.
Some content adapted from the Wikinfo article “Cascading Style Sheets” under the GNU Free Documentation License.
Overview
CSS is predominantly used by web page authors to define colors, fonts, layout, and other document characteristics. It is designed primarily to enable the separation of document structure (written in HTML or a related language) from document presentation (written in CSS). This separation provides a number of benefits, including improved content accessibility, greater flexibility and control in the specification of presentational characteristics, and reduced complexity of the structural content. CSS is capable of specifying auditory characteristics and other alternative rendering methods, in addition to its visual formatting capabilities.Advantages of using CSS include:
- Presentation information for an entire website or collection of pages resides in one place, and can be updated quickly and easily
- Different users can have different style sheets: large print and text readers for example. Web browsers allow users to specify their own local style sheet to apply to a remote site.
- The HTML code is reduced in size and complexity, since it does not need to contain any presentational markup
CSS has a syntax that is relatively simpler than that of HTML, and uses a number of English keywords to specify the names of various style properties. Here is a simple example of what CSS code looks like:
p { font-size: 110%; font-family: Garamond, serif; }
h2 { color: red; background: white; }
.highlight { color: red; background: yellow; font-weight: bold; }
h2 { color: red; background: white; }
.highlight { color: red; background: yellow; font-weight: bold; }
Here, the HTML elements
p
(paragraph) and h2
(level two heading) are being assigned stylistic attributes. The paragraph element will be rendered in a font size ten per cent larger than its parent, in the Garamond font or, if Garamond is unavailable, a generic serif font. The level two heading element will be rendered in red, on a white background. The third descriptor shown here defines a CSS class, which can be assigned to any HTML element by using the class
attribute. For example:
This paragraph will be rendered in red and bold, with a yellow background.
The CSS descriptors given above can be included within the HTML document, or imported separately. This capability gives CSS much of its flexibility and power. Additionally, CSS can be used with XHTML, XML, or in fact any structured document format which is properly implemented in an associated user agent or browser.
History of CSS
Style sheets have been around in one form or another since the beginnings of HTML in the early s. Various browsers included their own style language which could be used to customize the appearance of web documents. Originally, style sheets were targeted towards the end-user; early revisions of HTML did not provide many facilities for presentational attributes, so it was often up to the user to decide how web documents would appear.As the HTML language grew, however, it came to encompass a wider variety of stylistic capabilities to meet the demands of web developers. With these capabilities, style sheets became less important, and an external language for the purposes of defining style attributes was not widely accepted until the development of CSS.
The concept of Cascading Style Sheets was originally proposed in by . was at the time working on a browser called Argo which used its own style sheets; the two decided to work together to develop CSS.
A number of other style sheet languages had already been proposed, but CSS was the first to incorporate the idea of “” -- the capability for a document’s style to be inherited from more than one “style sheet.” This permitted a user’s preferred style to override the site author’s specified style in some areas, while inheriting, or “cascading” the author’s style in other areas. The capability to cascade in this way permits both users and site authors added flexibility and control; it permitted a mixture of stylistic preferences.
HÃ¥kon’s proposal was presented at the “Mosaic and the Web” conference in in , and again with Bert Bos in . Around this time, the World Wide Web Consortium was being established; the W3C took an interest in the development of CSS, and organized a workshop toward that end. HÃ¥kon and Bert were the primary technical staff on the project, with additional members, including Thomas Reardon of Microsoft, participating as well. By the end of 1996, CSS was nearly ready to become official. The CSS level 1 Recommendation was published in December .
Early in , CSS was assigned its own working group within the W3C, chaired by . The group began tackling issues that had not been addressed with CSS level 1, resulting in the creation of CSS level 2, which was published as an official Recommendation in May . CSS level 3 is still under development as of .
Difficulty with adoption
Although the CSS1 specification was completed in , it would be more than three years before any web browser achieved full implementation of the specification. Microsoft Internet Explorer 5.0 for the Macintosh shipped in March of , the first browser to have full (better than 99 per cent) CSS1 support. Other browsers followed soon afterwards, and many of them additionally implemented parts of CSS2, though as of , no browser has achieved full implementation of CSS2.Even the browsers that did achieve full implementation often did so with a degree of difficulty; many implementations of CSS are fraught with inconsistencies, bugs and other quirks. Authors have commonly had to utilize hacks and workarounds in order to obtain consistent results across browsers and platforms. One of the most well-known CSS bugs is the Internet Explorer box model bug; box widths are interpreted incorrectly in several versions of the browser, resulting in blocks which appear as expected in most browsers, but are too narrow when viewed in Internet Explorer. The bug can be avoided, but not without some cost in terms of functionality.
This is just one of hundreds of other CSS bugs that have been documented in various versions of Internet Explorer, Netscape, Mozilla, and Opera, many of which have severe detrimental effects on the legibility of the document; the proliferation of such bugs in CSS implementations has made it difficult for designers to achieve a consistent appearance across platforms. However, currently, Mozilla’s Gecko layout engine is the best at rendering CSS, while Internet Explorer remains the worst at rendering CSS by standards set down by World Wide Web Consortium.
Usage of CSS
CSS is designed primarily to separate presentation from content. Authors who use CSS commonly do so towards this end. Prior to CSS, nearly all of the presentational attributes of an HTML document were contained within the HTML code; all font colors, background styles, alignment specification, boxes, borders, and sizes had to be explicitly described, often repeatedly, in the midst of the HTML code. CSS allows authors to extract much of that information, resulting in considerably simpler HTML code, supplemented by an auxiliary style sheet written in the language of CSS. The structure and semantic markup is restricted to the HTML code, while the presentational markup is restricted to the CSS code.For example, the HTML element
h2
specifies that the text contained within it is a level two heading. It has a lower level of importance than h1
headings, but a higher level of importance than h3
headings. This aspect of the h2
element is structural.
Customarily, headings are rendered in decreasing order of size, with
h1
as the largest, because larger headings are usually interpreted to have greater importance than smaller ones. Headings are also typically rendered in a bold font in order to give them additional emphasis. The h2
element may be rendered in bold face, and in a font larger than h3
but smaller than h1
. This aspect of the h2
element is presentational.
Prior to CSS, document authors who wanted to assign a specific color, font, size, or other characteristic to all
h2
headings had to utilize the HTML font
element, or other presentational markup, in addition to the h2
element, since h2
is strictly a structural element. A heading to be rendered in an italic red font on a white background might be written:
Usage of CSS
The additional presentational markup in the HTML made documents more complex, and generally more difficult to maintain; if all level two headings were to be rendered in this style, the markup had to be used for each one separately. Furthermore, a person reading the page with a web browser loses control over the display of the text; if they would rather see the heading in blue, they cannot easily do so, as the site author has explicitly defined the heading color to be used.
With CSS, the
h2
element can be used to give the text structure, while the style sheet gives the text its presentational characteristics. The above might be written:
Usage of CSS
With an accompanying style sheet to define the red italic style and white background:
h2 { color: red; background: white; font-style: italic; }
Thus, presentation is separated from content. (It is because of the advantages offered by CSS that the W3C now considers many of the presentational elements and attributes in HTML to be deprecated). The HTML describes only structural aspects, and the CSS describes all presentational aspects. CSS can define color, font, text alignment, size, and also non-visual formatting such as the speed with which a page is read out loud in text readers.
CSS style information can be either attached as a separate document or embedded in the HTML document. Multiple style sheets can be imported, and alternative style sheets can be specified so that the user can choose between them. Different styles can be applied depending on what media is being used. For example, the screen version may be quite different from the printed version. This allows authors to tailor the presentation appropriately for each kind of media. Also, one of the goals of CSS is to allow users a greater degree of control over presentation; users who find the red italic headings difficult to read may apply their own style sheet to the document, and the presentational characteristics will be “cascaded”; the user may override just the red italic heading style, and the remaining attributes will stay the way they are.
Recommendations
The first CSS specification to become an official W3C Recommendation is CSS level 1, published in December . Among its capabilities are:- Font properties
- Color and background properties
- Text properties
- Box properties
- Classification properties
The W3C maintains the CSS1 Recommendation.
CSS level 2 was developed by the W3C and published as a Recommendation in May . A superset of CSS1, CSS2 includes a number of new capabilities, among them the absolute, relative, and fixed positioning of elements, the concept of media types, support for aural style sheets and bidirectional text, and new font properties such as shadows. The W3C maintains the CSS2 Recommendation.
CSS level 3 is currently under development. The W3C maintains a CSS3 progress report.
References
- : Forward Compatibility: Designing and Building with Web Standards., New Riders, ISBN 0735712018 (paperback) (book’s companion site)
- : Cascading Style Sheets: The Definitive Guide, 2nd Edition, O’Reilly & Associates, ISBN 0596005253
- Eric A. Meyer: Cascading Style Sheets 2.0 Programmer’s Reference, McGraw-Hill Osborne Media, ISBN 0072131780
External links
- Cascading Style Sheets at the W3C
- W3C CSS Validation Service
- A List Apart Magazine - Online magazine promoting the use of CSS and other web standards.
- css/edge - An amazing collection of examples showing what can be done with CSS.
- CSS2 tests by Peter-Paul Koch
- CSS Panic Guide - a fast resource
- CSS-discuss wiki - A wiki dedicated to CSS
- css Zen Garden - A demonstration of what can be accomplished visually through CSS&8211;based design.
- XML.com
Hacks and workarounds
Some content adapted from the Wikinfo article “Cascading Style Sheets” under the GNU Free Documentation License.