CSS权威指南(第3版)：2006年英文版基石

5星 · 超过95%的资源需积分: 0 153 浏览量更新于2024-07-24 4 收藏 7.01MB PDF 举报

《CSS权威指南(第3版,2006)》是一本深入介绍层叠样式表(CSS)的经典著作，英文版提供了全面而详实的技术指导。该书作为O'Reilly出版社的标志性作品之一，针对网页设计和开发人员，详细讲解了CSS语言的核心概念、选择器、属性、布局、样式的继承与优先级以及响应式设计等核心内容。它不仅阐述了CSS的基础理论，还包含了丰富的实战示例和最佳实践，帮助读者掌握如何有效地运用CSS来提升网站的可读性、可维护性和性能。与其他O'Reilly系列书籍如《HTML & XHTML: The Definitive Guide》、《JavaScript: The Definitive Guide》和《Learning JavaScript》形成互补，这些书籍构成了前端开发者的知识体系。《Dynamic HTML: The Definitive Reference》和《JavaScript & DHTML Cookbook™》则深入探讨了动态网页技术，而《Web Design in a Nutshell》则是网页设计入门的实用指南。 O'Reilly官网oreilly.com不仅是其众多图书的在线目录，还提供了新闻更新、活动信息、技术文章、博客链接、章节样本和代码示例，为开发者提供了丰富的学习资源和最新技术资讯。对于对开放和新兴技术感兴趣的开发者，oreillynet.com是不可或缺的门户，这里涵盖了新平台、编程语言和操作系统等内容。此外，O'Reilly举办的各类会议，如conferences.oreilly.com上，汇集了行业的创新者，共同推动技术发展并分享革新思想。SafariBookshelf（safari.oreilly.com）作为在线编程和IT专业人员的首选参考库，订阅用户可以实时搜索超过1000本书，获取即时的答案和解决方案。《CSS权威指南(第3版,2006)》是一本权威且实用的CSS教材，适合从初学者到高级开发者的不同层次阅读，通过它，读者可以深入了解CSS并将其应用于实际项目中，以实现高效、优雅的网页设计和开发。同时，O'Reilly提供的全方位资源和服务为学习者提供了一个完整的知识网络。

xiv

Preface

If you feel your use of code examples falls outside fair use or the permission given

above, feel free to contact us at permissions@oreilly.com.

How to Contact Us

We at O’Reilly 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 Media, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

800-998-9938 (in the United States or Canada)

707-829-0515 (international or local)

707-829-0104 (fax)

There is a web page for this book, which lists errata, examples, or any additional

information. You can access this page at:

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

To comment or ask technical questions about this book, send email to:

bookquestions@oreilly.com

For more information about books, conferences, Resource Centers, and the O’Reilly

Network, see the O’Reilly web site at:

http://www.oreilly.com

Safari® Enabled

When you see a Safari® Enabled icon on the cover of your favorite tech-

nology book, that means the book is available online through the

O’Reilly Network Safari Bookshelf.

Safari offers a solution that’s better than e-books. It’s a virtual library that lets you

easily search thousands of top tech books, cut and paste code samples, download

chapters, and find quick answers when you need the most accurate, current informa-

tion. Try it for free at http://safari.oreilly.com.

Acknowledgments

I’d like to take a moment to thank the people who have backed me up during the

long process of getting this book to its readers.

Preface

First, I’d like to thank everyone at O’Reilly for all they’ve done over the years, giving

me my break into publishing and continuing to give me the opportunity to produce a

book that matters. For this third edition, I’d like to thank Tatiana Apandi for her

good humor, patience, and understanding as I played chicken with my deadlines.

I’d also like to thank most profoundly my technical reviewers. For the first edition,

that was David Baron and Ian Hickson, with additional input from Bert Bos and

Håkon Lie. The second edition was reviewed by Tantek Çelik and Ian Hickson. The

fine folks who performed technical review on the third edition, the one you hold in

your hands, were Darrell Austin, Liza Daly, and Neil Lee. All lent their considerable

expertise and insight, keeping me honest and up-to-date on the latest changes in CSS

as well as taking me to task for sloppy descriptions and muddled explanations. None

of the editions, least of all this one, could have been as good as it is without their col-

lective efforts, but of course whatever errors you find in the text are my fault, not

theirs. That’s kind of a cliché, I know, but it’s true nonetheless.

Similarly, I’d like to thank everyone who pointed out errata that needed to be

addressed. I may not have always been good about sending back email right away,

but I read all of your questions and concerns and, when needed, made corrections.

The continued feedback and constructive criticism will only help the book get bet-

ter, as it always has.

There are a few personal acknowledgments to make as well.

To the staff of WRUW, 91.1 FM Cleveland, thank you for nine years of support,

great music, and straight-out fun. Maybe one day I’ll bring Big Band back to your air-

waves, and maybe not; but either way, keep on keepin’ on.

To Jeffrey Zeldman, thanks for being a great colleague and partner; and to the whole

Zeldman family, thanks for being such wonderful friends.

To “Auntie” Molly, thanks for always being who you are.

To “Uncle” Jim, thanks for everything, both professionally and personally. It’s no

exaggeration to say I wouldn’t be where I am without your influence, and our lives

would be a good deal poorer without you around.

To the Bread and Soup Crew—Jim, Genevieve, Jim, Gini, Ferrett, Jen, Jenn, and

Molly—thanks for all your superb cooking and tasty conversation.

To my extended family, thank you as always for your love and support.

To anyone I should have thanked, but didn’t: my apologies. And my thanks.

And to my wife and daughter, more thanks than I can ever express for making my

days richer than I have any right to expect, and for showering me with more love

than I could ever hope to repay. Though I’ll keep trying, of course.

—Eric A. Meyer

Cleveland Heights, Ohio

1 August 2006

Chapter 1

CHAPTER 1

CSS and Documents

Cascading Style Sheets (CSS) are a powerful way to affect the presentation of a docu-

ment or a collection of documents. Obviously, CSS is basically useless without a doc-

ument of some sort, since it would have no content to present. Of course, the

definition of “document” is extremely broad. For example, Mozilla and related

browsers use CSS to affect the presentation of the browser chrome itself. Still, with-

out the content of the chrome—buttons, address inputs, dialog boxes, windows, and

so on—there would be no need for CSS (or any other presentational information).

The Web’s Fall from Grace

Back in the dimly remembered, early years of the Web (1990–1993), HTML was a

fairly lean language. It was composed almost entirely of structural elements that were

useful for describing things like paragraphs, hyperlinks, lists, and headings. It had

nothing even remotely approaching tables, frames, or the complex markup we

assume is necessary to create web pages. HTML was originally intended to be a

structural markup language, used to describe the various parts of a document; very

little was said about how those parts should be displayed. The language wasn’t con-

cerned with appearance—it was just a clean little markup scheme.

Then came Mosaic.

Suddenly, the power of the World Wide Web was obvious to almost anyone who

spent more than 10 minutes playing with it. Jumping from one document to another

was no more difficult than pointing the cursor at a specially colored bit of text, or

even an image, and clicking the mouse. Even better, text and images could be dis-

played together, and all you needed to create a page was a plain-text editor. It was

free, it was open, and it was cool.

Web sites began to spring up everywhere. There were personal journals, university

sites, corporate sites, and more. As the number of sites increased, so did the demand

for new HTML elements that would each perform a specific function. Authors

started demanding that they be able to make text boldfaced or italicized.

Chapter 1: CSS and Documents

At the time, HTML wasn’t equipped to handle those sorts of desires. You could

declare a bit of text to be emphasized, but that wasn’t necessarily the same as being

italicized—it could be boldfaced instead, or even normal text with a different color,

depending on the user’s browser and preferences. There was nothing to ensure that

what the author created was what the reader would see.

As a result of these pressures, markup elements like

<FONT>

and

<BIG>

started to creep

into the language. Suddenly, a structural language started to become presentational.

What a Mess

Years later, we have inherited the problems of this haphazard process. Large parts of

HTML 3.2 and HTML 4.0, for example, were devoted to presentational considerations.

The ability to color and size text through the

font

element, to apply background colors

and images to documents and tables, to use

table

attributes (such as

cellspacing

), and

to make text blink on and off are all the legacy of the original cries for “more control!”

For an example of the mess in action, take a quick glance at almost any corporate

web site’s markup. The sheer amount of markup in comparison to actual useful

information is astonishing. Even worse, for most sites, the markup is almost entirely

comprised of tables and

font

elements, neither of which conveys any real semantic

meaning as to what’s being presented. From a structural standpoint, these pages are

little better than random strings of letters.

For example, let’s assume that for page titles, an author uses

font

elements instead of

heading elements like

<font size="+3" face="Helvetica" color="red">Page Title</font>

Structurally speaking, the

font

tag has no meaning. This makes the document far less

useful. What good is a

font

tag to a speech-synthesis browser, for example? If an

author uses heading elements instead of

font

elements, though, the speaking browser

can use a certain speaking style to read the text. With the

font

tag, the browser has

no way to know that the text is any different from other text.

Why do authors run roughshod over structure and meaning this way? Because they

want readers to see the page as they designed it. To use structural HTML markup is

to give up a lot of control over a page’s appearance, and it certainly doesn’t allow for

the kind of densely packed page designs that have become so popular over the years.

But consider the following problems with such an approach:

• Unstructured pages make content indexing inordinately difficult. A truly power-

ful search engine would allow users to search only page titles, or only section

headings within pages, or only paragraph text, or perhaps only those paragraphs

that are marked as important. To accomplish such a feat, however, the page con-

tents must be contained within some sort of structural markup—exactly the sort

of markup most pages lack. Google, for example, does pay attention to markup

structure when indexing pages, so a structural page will increase your Google rank.

剩余537页未读，继续阅读

Zachshelter

粉丝: 2
资源: 1

CSS权威指南(第3版)：2006年英文版基石

css权威指南英文版

css权威指南第四版 CSS The Definitive Guide 英文版

CSS权威指南英文版 第四版 2017年编写

hadoop.the.definitive.guide.4th.edition.1491901632

the definitive guide to dax (2nd edition).pdf

入门学习CSS推荐那几本书

帮我找到一本书《Ethernet. The Definitive Guide》

html,css,javascript,node.js,Mysql数据库的参考文献

基于html和css开发的书籍列表

arm cortex-m3与cortex-m4权威指南英文原版叫什么

最新资源

CSS权威指南英文版第四版 2017年编写