| Today both Netscape and Microsoft have agreed to | | | | within one browser, you can most likely use a CSS |
| implement CSS in their respective browsers and this | | | | element to set it, too. For example, the |
| means that Web authors who want to use CSS | | | | TEXTDECORATION element has a value called BLINK |
| have to knowwhich CSS elements they can and can't | | | | that flashes the text on and off repeatedly. It is |
| use, as well as the significant differencesin the way | | | | supported within Netscape Navigator - where |
| adopted CSS elements behave in both browsers. | | | | youcould use the tag to do much the same sort of |
| Both use only a subset of the complete specification | | | | thing - but not in Internet Explorer, which has never |
| as laid out by the W3C. Since both companiesare | | | | supported . On the other hand, there is a feature |
| members of the W3C, however, they will adopt the | | | | seen only in Internet Explorer called "watermarking" |
| full set of CSS elements over time - at least that is | | | | that allows the Web author to create a background |
| the hope. CSS1 (and CSS2) will only be useful to Web | | | | image that remains fixed upon the page even when |
| authors if they are widely adopted and fully | | | | a user scrolls up or down. There is a CSS value |
| implemented by browser manufacturers. If they are | | | | ("BACKGROUND-ATTACHMENT: FIXED") that does |
| not, CSS could easily disappear. There is a precedent | | | | the same thing. |
| for this: the official HTML 3.0 specification was widely | | | | Not surprisingly,this CSS element is supported within |
| ignored by browser manufacturers. | | | | Internet Explorer, but not within Netscape Navigator. |
| The piecemeal way in which Netscape Navigator and | | | | Knowing which CSS elements to use and which not |
| Internet Explorer have adopted CSS elements is | | | | to use is half the battle in constructing workable CSS |
| holding CSS back from wider adoption within the | | | | code. It can only be hoped that over time all CSS |
| Web authoring community. In many cases, CSS | | | | elements will be supported equally well within the two |
| elements that are supported in Internet Explorer are | | | | major browsers.As time goes by and more Web |
| not supported in Netscape Navigator, or they are not | | | | authors become familiar with the details of CSS (and |
| supported in either browser. Sometimes only certain | | | | as more Web browsers fully implement and are able |
| values of a CSS element are supported, or they only | | | | to display Web pages that use CSS), the demand |
| work when associated with certain HTML tags. There | | | | and need for new HTML tags will be significantly |
| are even cases where a CSS element has been | | | | diminished. Depending on how things turn out, CSS will |
| adopted for use within a beta (or "preview") version | | | | either be a triumph or a resounding failure for the |
| of a browser and then later dropped in the next beta | | | | W3C, ultimately determining the evolution and |
| release - presumably an oversight, but not exactly | | | | development of HTML and of the relevancy of the |
| something to inspire confidence in CSS for a Web | | | | W3C itself. |
| author. | | | | An understanding of the strengths and weaknesses |
| There are also significant differences in the way CSS | | | | of a given browser will help you to choose which |
| code works in the same browser operating under | | | | CSS elements will be most effective inyour Web |
| different operating systems. | | | | pages. |
| In general, if a certain feature is already supported | | | | |