HTML and CSS Reference
value avoid will cause browsers to attempt not to generate a page break,
however, and as the name avoid implies, it is just an attempt and not
an absolute rule.
Browser support for the page break properties is quite mixed, and
some browsers have more complete support for individual values than
others. You can find a good breakdown and notes on support for the
page break-related properties at the Sitepoint CSS Reference ( http://
The @page rule exists as a way of setting properties of the page such as
margins or orientation. At the time of this writing, the features of @page
from CSS2 and CSS3 are quite poorly supported (Opera being the one
shining star), so it isn't worth presenting the properties in detail.
The presentation, width, color schemes, navigational elements, and other
design features of many web pages may be appropriate for the screen,
but not as much when printed. If someone is printing out an article,
recipe, or event information from your web site, the last thing they are
looking for is half the first page taken up by navigation and advertis-
ing and an extra page at the end taken up with nothing but the footer
content and repeated navigation links.
To prepare pages for print, a few types of styles are often changed to
provide the best printed experience (and not waste your visitor's paper
■ Hide the sidebar, navigation, or other site “meta” elements that are
presented on the screen to help when interacting with the site on
the screen. Branding elements, logos, and legal information are still