Almost. Properties are separated from their values by colons:
Originally Posted by Mazigh
True. It also makes presentational changes to a well-written document very easy as only the style sheet needs to be altered and will be propagated through the entire site automatically.
I also know that the css is useful, since you don't have to type all the html-tags in all you documents and at every link/alinea/head/background..., for this reason your page will take less time to load itself.
If you prefer to think of them as categories, that's you're perogative, but I would advise you to always use the correct terms. If you asked a question about 'CSS categories' I wouldn't have a clue what you meant.
but i knew that those properties have several selector(what i call categories)
A couple of comments.
- Don't use pixels (or points; pt) to size text. IE has a bug which makes it difficult for users to resize text using the 'Text Size' menu item. This is potentially very bad for usability. Instead, use percentages. Body text should be left at 100% of the default, with legalese (and the like) smaller but no lower than 85% of that default.
- On a related note, don't use Verdana, at least if you feel that you need to reduce it's size. Verdana is not a universally available font and it has different characteristics to most others. Though it may be readable (for many, not all) at 12px, a replacement font may be far too small.
Removing the underline from links...
...and making them appear the same colour as other text is usually a very bad idea. Links should be easily recognisable within text. You might understand the rendered result of this rule to indicate a link, but your visitors may just see them as bold text.
A further note: when specifying a foreground colour, the background colour should also be included as well (and visa versa). The default colours in your browser might be black-on-white, but not everyone's will be and clashes can make a site unreadable. The only exception to this guideline is when another rule already specifies both. For example:
The first rule will render all paragraph text as black-on-white. Paragraphs that contain a warning should be displayed as red-on-white. As the first rule already specifies that background colour, there's no (current) need to it in the second rule, too.
The CSS specification devotes an entire section to selectors. I think it's very readable, but ask if you have problems. What I will say, though, is that only decent browsers support all of the types listed there. IE is not a decent browser, and fails to support many including the adjacent, child, attribute, lang(), and first-child selectors. It will also only support the interactive pseudo-classes with links (a elements). That just leaves the universal, element, descendant, link pseudo-class, class, and id selectors. Other older browsers will have similar limitations.
So, my question is: where i can find a page about all those categories (or at least the important categories/selectors) ?