|
The Bottom Line (on this page) -
Five Rules to keep us stay sane.
New rules - use lower-case for tags, and remember to close them all.
If your STYLE code will not work (and there is no recognised Bug involved - signalled by the rose), sometimes placing the attribute value in parenthesis (inner quote signs) solves the problem. Make sure all quote signs are in pairs (remember to close them!).
So let's see the Five Rules:
Rule 1. ANY browser should be able to access the content of the site.
Rule 2. Rule 1 does NOT imply that the site should look the same in each browser.
Rule 3. If something non-essential does not work in a certain browser, Too Bad For That Browser.
Rule 4. Always check style sheets in Netscape 4 first. Style sheets may break in most browsers, but if they break in Netscape 4 they break really spectacularly.
Rule 5. Know when to stop. Sometimes, trying to apply a particular style is just more trouble than it's worth.
These rules are not absolute. They're meant to give you something to hold on to when you first use style sheets. Rules Three and Five, especially, give you plenty of leeway for interpretation. After all, each site is unique, both in its design and in the exact mix of browsers that visit it.
Today is only the dawning of the Style Sheet Era not yet even the morning.
There's still plenty of time for experimenting, and disagreeable results can still be hidden in the darkness. The only thing a web designer should do right now is stay informed and experiment, so that when the sun breaks through at last you can say to your clients and co-workers, "I knew Style Sheets were the future." Be prepared. -
Some new ideas
CSS style sheets should use lower case element and attribute names. XHTML is case sensitive, and we want to be understood when that new wave hits.
Early in 2001, when I started this project, CSS was to be the answer to the problems of differing Browsers (according to writers in items dated last century, eg 1999).
BUT the goal posts have moved - media for viewing Web Pages is evolving and the markup language needs to adjust.
The next game is called XHTML 1.0: The Extensible HyperText Markup Language, meant to be A Reformulation of HTML 4 and easy to learn! - from the W3C Recommendation 26 January 2000.
Understanding CSS development
http://www.w3.org
The CSS3 module describes the various values and units that CSS
properties accept. Also, it describes how "specified values", which is what a
style sheet contains, are processed into "computed values" and "actual
values".
The working draft consists of 24 files. Some are very large, for example the page on FONTS is 140KB. I have tried to pick out the basics. Go to the source to develop your wisdom.
Status of the official document
The W3C Working Draft, 13 July 2001, location
- This version:
- http://www.w3.org/TR/2001/WD-css3-values-20010713
- Latest version:
- http://www.w3.org/TR/css3-values
This is a draft of a module
of CSS level 3. It will probably be bundled with some other modules
before it becomes a W3C
Recommendation.
All the properties and features described here that also exist in CSS
level 2 are intended to be backwards compatible. (There are actually no new
features in this draft, it only serves to rewrite the relevent parts of CSS
level 2 in the form of a CSS3 module, but in future versions there will be.)
This draft should not be cited except as "work in progress." It is a work
item of the CSS working group and part of the Style
activity. It may be modified or dropped altogether at any point in time.
Implementations for the purpose of experimenting with the specification are
welcomed, as long as they are clearly marked as experimental.
Feedback on this draft is invited. The preferred place for discussion is
the (archived)
public mailing list www-style@w3.org. W3C members can also send comments to the
CSS WG mailing list.
A list of current W3C Recommendations and other technical documents
including Working Drafts and Notes can be found at http://www.w3.org/TR.
|