When it comes right down to it, positioning is a very compelling technology. It's also likely to be an exercise in frustration if you're trying to get it to behave consistently in a cross-browser environment. The problem isn't so much that it won't work in some browsers: it's that it will only sort of work in a number of them, such as Navigator 4 and Internet Explorer 4 and 5. It can be great fun to play with positioning, and one day we'll be able to use it in place of tables and frames while dramatically improving accessibility and backward compatibility. As of this writing, though, it remains a great way to create design prototypes, but a tricky thing to use on a public web site.
As it happens, this sentiment may be applied to the majority of CSS2, which is given an overview in the next chapter.
This appendix lists all CSS1 properties, plus the CSS1pseudo-elements and pseudo-classes. The values to the right of aproperty name show the browser compatibility information for thatproperty. They will look something like this:
The first value in each pair is for the Windows version; the secondvalue is for the Macintosh version. (Sorry, Macintosh folks, but weare in the minority.) For instance, IE4 Y/N means that the propertyis supported in IE4 for Windows, but not IE4 for Macintosh. Thepossible support values are:
Copyright © 2002 O'Reilly & Associates. All rights reserved.spill beyond the browser window is entirely dependent on the width ofthe window itself -- and the wider the window, the worse thesituation becomes.
Using negative margins with block-level elementssuch as these can quite obviously be dangerous and is rarely worththe trouble -- but it can also be rewarding. It takes a good dealof practice, and many mistakes, to learn to tell the differenceproperty is used to select that face.
What happens if no such face exists? There are two options providedin the specification. The first is for the user agent to create asmall-caps face by scaling uppercase letters on its own. The secondis simply to make all letters uppercase and the same size, exactly asif the declaration text-transform:uppercase; had been used instead, as shown inFigure 5-30. This is obviously not an idealsolution, but it is permitted.