Book HomeCascading Style Sheets: The Definitive GuideSearch this book Friday 12th of February 2016 10:33:26 AM

0.3. How to Contact Us

We have tested and verified the information in this book to the best of our ability, but you may find that features have changed (or even that we have made mistakes!). Please let us know about any errors you find, as well as your suggestions for future editions, by writing to:

O'Reilly & Associates, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

(800) 998-9938 (in the U.S. or Canada)

(707) 829-0515 (international/local)

(707) 829-0104 (fax)

You can also send us messages electronically. To be put on the mailing list or request a catalog, send email to:

To ask technical questions or comment on the book, send email to:

below the bottom of the former.

This rule prevents floated elements from overwriting each other. If an element is floated to the left, and there is already a floated element there due to its earlier position in the document source, then the latter element is placed against the outer right edge of the previously floated element. If, however, a floated element's top is below the bottom of all earlier floated images, then it can float all the way to the inner left edge of the parent. Some examples of this are shown in Figure 8-31.

We have a web site for the book, where we'll list examples, errata, and any plans for future editions. You can access this page at:

http://www.oreilly.com/catalog/css/

For more information about this book and others, see the O'Reilly web site:

http://www.oreilly.com/



Library Navigation Links

Copyright © 2002 O'Reilly & Associates. All rights reserved.

Figure 7-26

Figure 7-26. Navigator 4.x and margins

If you want to overcome this space, you can always use negativemargins. Here's one possible declaration:

H1 {margin-bottom: 0;}P {margin-top: -1em;}

The problem with this solution arises when the document is viewed inInternet Explorer, which will displaywhat's shown in Figure 7-27. The overlappingauto. This allows user agents to determine whatbehavior to use, although they are encouraged to provide a scrollingmechanism when necessary. This is a potentially useful way to useoverflow, since user agents could interpret it tomean "provide scrollbars only when needed." (They maynot, but they certainly could, and probably should.)

In the simplest case, the clipping region for any positioned elementis the content area of the element itself, as depicted in Figure 9-10. However, you may wish to change the clippingarea. That's what we'll do in the next section.need to explicitly declare a width as well, like so: width: 10em . To be honest, I'm not sure why this should permit floating where it wouldn't otherwise happen. It does make some sense, given the usual desire for declaring a width on floated text elements in any case, but the specification does not require that a width be declared in order to make a text element float successfully. Internet Explorer 4.x for Windows does.