Friday 15th of December 2017 08:50:40 PM
What CSS looks like
- A Basic Style Sheet
- Note that the BODY declaration establishes the font family, text color, and background color. Any “child” of the BODY declaration (such as
<blockquote>) will use these same fonts and colors unless the Style Sheet specifies otherwise. In CSS, this passing of characteristics from “parent” to “child” is called inheritance.
because most letters are not as wide as they are tall, but of course
you may use other values; experiment to see what you like best.
11.2.10. Disappearing Styles
Here's a rather obscure Navigator
bug which is utterly baffling when encountered. Under whatever
Notice that p and li reproduce the font-family information already declared by BODY. According to the rules of inheritance, this should not be necessary. Unfortunately, this redundancy is required to work around the defects of Netscape Navigator 4, which ignores inheritance because it lacks even the most basic CSS compliance.
A Sophisticated Style Sheet (offsite link)
Demonstrating how CSS can entirely replace (X)HTML table layouts. View alistapart.com in a CSS–capable browser (IE5+, Netscape 6+, Mozilla, Opera 5) to see how the Style Sheet creates the page layout. (View the same site in IE4 or Netscape 4 to see how the layout is hidden from those browsers, since they are incapable of reproducing it.)
Notice also that browser offsets have been turned off via the margin and padding declarations. These declarations replace non-standard attributes to the HTML BODY tag, such as “marginheight” and “marginwidth,” which should never, never, never be used.
CSS Usage at NYPL
View Source, and you'll see that this Style Guide has been laid–out entirely with CSS (no (X)HTML table hacks). Alas, for the foreseeable future, most Library projects will employ a combination of CSS and XHTML tables, in order to accommodate non-CSS-compliant browsers such as Netscape Navigator 4 and Microsoft Internet Explorer 4.
Tables and Accessibility
Although XHTML table layouts are less accessible than pure CSS layouts, and although they require additional markup (and thus use more bandwidth), it is entirely possible to create valid XHTML table layouts that work in combination with valid Style Sheets—and that is what this Style Guide recommends.
On the next page, we explore CSS resources to help you learn more. »
« CSS Section Index | CSS Guidelines 3 »
|Here's a link to the <A HREF="#top">top of
In the second one, however, the place where the boldface element
would have appeared is simply closed up, and the positioned text
overlaps the some of the content. There is no way to avoid this,
short of positioning the boldfaced text outside of the paragraph (by
using a negative value for right) or by specifying
a padding for the paragraph that is wide enough to accommodate the
positioned element. Also, since it has a transparent background, the
parent element's text shows through the positioned element. The
only way to avoid this is to set a background for the positioned
this page.</A> (I stuck a hidden anchor tag there:
Use anchors to improve navigability, but remember that multiple
linked pages will download quicker than one huge page requiring lots of