Sunday 25th of February 2018 10:05:47 PM

Book Home

Cascading Style Sheets: The Definitive GuideSearch this book

Symbols | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

Index: F

fictional tags (see pseudo-element selectors)

Of course, it's still possible to use these properties to keepan element from exceeding a certain size, as in this:

max-height: 30em; max-width: 20em;

The question here, though, is what happens if the content of theelement doesn't all fit into the specified element size. Doesit get cut off at the boundaries, or does it spill outside thepositioned element? That's what the next section will

file size with CSS: 1.2.5. Compact File Size
decreased: 11.1.2. Case 2: Library Catalog System Interface
:first-child pseudo-element: 10.2.3.4. :first-child
:first-letter pseudo-element: 2.4.2. Pseudo-Element Selectors
first line of paragraph, indenting: 4.1.1.1. Indenting text
:first-line pseudo-element: 2.4.2. Pseudo-Element Selectors
:first pseudo-class: 10.2.3.5. Miscellaneous pseudo-elements and pseudo-classes
fixed positioning: 9.4. Fixed Positioning
float property: 7.6. Floating and Clearing
floated elements: 7.6. Floating and Clearing
8.3. Floated Elements
applied behavior: 8.3.2. Applied Behavior
background and: 7.6.1.1. Backgrounds and floats
8.3.2. Applied Behavior
clearing: 7.6.2. Clear
collapsing margins and: 7.6.1. Floated Elements
columns and: 11.1.3. Case 3: Putting a Magazine Article Online
images: 7.6. Floating and Clearing
Internet Explorer 4.x and: 11.2.8. Floating Text Elements in Internet Explorer
min-max properties and: 9.1.3.2. Limiting width and height
negative margins and: 7.6.1.2. Negative margins and floating
8.3.2.1. Negative margins
overlapping, preventing: 8.3.1. Floating: The Details
placement, rules governing: 8.3.1. Floating: The Details
taller than parent element: 8.3.2. Applied Behavior
wider than parent element: 8.3.2.1. Negative margins
:focus pseudo-element: 10.2.3.2. :focus
font declaration, forward-slash in: 2.1.3. Declarations
font faces: 5.1. Font Families
font families: 5.1. Font Families
declarations, quotation marks in: 5.1.3. Using Quotation Marks
generic: 5.1. Font Families
combining with actual: 5.1.2. Specifying Actual Font Names
importance of providing: 5.1.2. Specifying Actual Font Names
specifying: 5.1.2. Specifying Actual Font Names
font-family property: 5.1.1. Using Generic Font Families
font matching: 5.6. Font Matching
font names (see font families)
font property: 5.5. Using Shorthand: The font Property
required values: 5.5. Using Shorthand: The font Property
values new with CSS2: 10.3. Fonts and Text
font-size-adjust property: 10.3.1. New Font Properties
font-size property: 5.3. Font Size
font sizes: 5.3. Font Size
absolute: 5.3.1. Absolute Sizes
inheritance and: 5.3.4. Font Size and Inheritance
percentage values: 5.3.3. Percentages and Sizes
relative: 5.3.2. Relative Sizes
setting using length units: 5.3.5. Using Length Units
font-stretch property: 10.3.1. New Font Properties
font-style property: 5.4.1. Fonts with Style
font-variant property: 5.4.2. Font Variations
font-weight property: 5.2. Font Weights
fonts: 5. Fonts
alternate, providing: 5.1.2. Specifying Actual Font Names
5.1.4. Good Practices
families (see font families)
fantasy: 5.1. Font Families
handling in CSS specifications: 1.3.1. Limited Initial Scope
kursiv: 5. Fonts
matching: 5.6. Font Matching
naming issues: 5. Fonts
sizes (see font sizes)
styles: 5.4.1. Fonts with Style
variants: 5.4.2. Font Variations
weights: 5.2. Font Weights
how they work: 5.2.1. How Weights Work
sample, list of: 5.2.1. How Weights Work
footer of a table: 10.7. Tables
foreground colors: 6.1.1. Foreground Colors
importance of declaring background color with: 6.1.4. Good Practices
foreign languages
default text alignment in Arabic/Hebrew: 4.1.1.2. Aligning text
hyphenation in: 4.1.1.2. Aligning text
:lang pseudo-class: 10.2.3.3. :lang
form elements
background images, placing in: 6.2.1. Background Images
color, setting: 6.1.1.4. Affecting form elements
forward slash (/)
font property and: 5.5.1. Adding the Line Height
separating keywords: 2.1.3. Declarations
frequency values: 3.5. CSS2 Units


Symbols | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z


Library Navigation Links

Copyright © 2002 O'Reilly & Associates, Inc. All Rights Reserved.

BODY {color: red;}TABLE {color: black;}

That's because the combination of your style, and thebrowser's built-in styles looks like Figure 6-10.

Figure 6-10

Figure 6-10. The result of combining author styles and browser styles

Since there is a color value defined by thebrowser for TABLE elements, it will takeprecedence over the inherited value. This is annoying andunnecessary, but it is an obstacle to be overcome. You can overcome XML documents are also naturally committed to a database (relational or object) or any other kind of XML document store. There are commercial products available which allow you to save XML documents to an XML storage layer (which is not a database per se), like Datachannel's XStore and ODI's eXcelon. These XML store solutions are quite expensive ($10,000 to $20,000 range).

XML documents are also quite naturally retrieved from a persistence layer (databases, file systems, XML stores). This lends XML to be used in real world applications where the information being used by different parts of a system is the most important thing.

XML is platform independent, textual information

Information in an XML document is stored in plain-text. This might seem like a restriction if were thinking of embedding binary information in an XML document. There are several advantages to keeping things plain text. First, it is easy to write parsers and all other XML enabling technology on different platforms. Second, it makes everything very interoperable by staying with the lowest common denominator approach. This is the whole reason the web is so successful despite all its flaws. By accepting and sending information in plain text format, programs running on disparate platforms can communicate with each other. This also makes it easy to integrate new programs on top of older ones (without rewriting the old programs), by simply making the interface between the new and old program use XML.

For example, if you have an address book document stored in an XML file, created on a Mac, that you would like to share with someone who has a PC, you can simply email them the plain text address book XML document. This cant be done with binary encoded information which is totally platform (and program) dependent.