Thursday 23rd of March 2017 09:02:07 PM

by Eric A. Meyer
ISBN 1-56592-622-6
First edition, published May 2000.
(See the catalog page for this book.)

Search the text of Cascading Style Sheets: The Definitive Guide.

Table of Contents

Copyright Page
Preface
Chapter 1: HTML and CSS
Chapter 2: Selectors and Structure
Chapter 3: Units and Values
Chapter 4: Text Properties
Chapter 5: Fonts
Chapter 6: Colors and Backgrounds
Chapter 7: Boxes and Borders
Chapter 8: Visual Formatting
Chapter 9: Positioning
Chapter 10: CSS2: A Look Ahead
Chapter 11: CSS in Action
Appendix A: CSS Resources
Appendix B: HTML 2.0 Style Sheet
how to change the position of the origin image, we need to figure out how user agents will handle the situation.

It will be easier to show an example, and then explain it. Consider the following, which is illustrated by Figure 6-49:

BODY {background-image: url(bg23.gif);
background-repeat: repeat-y;
background-position: center;}
Figure 6-49

Figure 6-49. Centering the origin image and repeating vertically

Appendix C: CSS1 Properties
Appendix D: CSS Support Chart
Index
Colophon
Library Navigation Links

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

designed to address this issue, such as marker-offset. Since this property and its cousins are not widely supported at the time of this writing, we will not spend time on it here. There is a brief discussion of the marker properties in Chapter 10, "CSS2: A Look Ahead".

8.2.4. Block-Level Replaced Elements

Block-level neither is declared, then both will default to 0(zero). This assumes that no style is set for the border. If a borderstyle is set, then the value of border-widthdefaults to medium , not zero. The exact width ofmedium will depend on the user agent'sprogramming, but a common value is 2 or 3 pixels.

of text/css in the LINK element. So make sure you name your style sheets appropriately.

1.4.1.1. LINK attributes

For the rest of the LINK tag, the attributes and values are fairly straightforward. REL stands for "relation," and in this case, the relation is "stylesheet."

Web-based applications are similar to app servers, except for one thing: Web-based applications don't have client apps, instead they use web browsers on the client side. They generate their front ends using HTML, which is dynamically generated by the web-based app. In the Java world, Servlets are best suited for this job.

Web-based apps might themselves rely on another app server to gather information that is presented on the client web browser. Also, you can write Servlets that get information from remote or local databases, XML document repositories and even other Servlets. One good use for web-based apps is to be a wrapper around an app server, so that you can allow your customers to access at least part of the services offered by your app server via a simple web browser. So web-based apps allow you to integrate many components including app servers, and provide access to this information over the web via a simple web browser.

Web-based apps are very deployable, since they don't require special Java VMs to be installed on the client side, or any other special plug ins, if the creator of the web-based app relies solely on HTML. Unfortunately, this can restrict the level of service that can be offered by a web-based app when compared to the functionality offered by custom clients of an app server, but they are a good compromise when it comes to providing web-based access to your information. In fact, in a real world scenario, both a web-based app and app server may be used together, in order to provide your customers access to their information. In an Intranet setting, you might deploy the clients that come with the app server, and in an Internet setting it would be better to deploy a web-based app that sits on top of this app server, and gives your customers (relatively) limited access to their data over the web (via a simple web browser).

If 300 is unassigned, it is given the next variantlighter than 400. If no lighter variant isavailable, 300 is assigned the same variant as400. In this case, it will usually be"Normal" or "Medium." This method is alsoused for 200 and 100.

  • If 600 is unassigned, it is given the next variantdarker than 400. If no darker variant is