HTML5真相：现在与未来

需积分: 0 175 浏览量更新于2024-07-18 收藏 5.44MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

Chapter 1 ■ a Somewhat SenSationalized hiStory of html5

WHATWG and W3C Diversions

In September 2012 the W3C introduced its own team of editors, deposing Hixie as the king supreme of HTML5,

at least in theory. The W3C explained the decision as one made at Hickson’s request in a blog post in April 2012

(http://lists.w3.org/Archives/Public/public-html/2012Apr/0204.html):

We have reached a point in the HTML WG where the W3C process and community expects to

finalize the HTML 5 Recommendation-track specifications. For the last several years, Ian Hickson

has been the editor of the HTML 5 spec. At the same time, we all recognize that work will begin

on ‘what will come after HTML 5’. As Ian is already working on proposals for this work, he has

asked the chairs if someone else could volunteer to take the HTML 5 spec to REC. Today, we are

announcing the following changes:

* W3C is starting a search for editors to begin the REC level work on HTML5 and HTML Canvas 2D

Context. We anticipate this search will take 30 days.

* Anyone is welcome to contribute proposals that could be used as input for future products of the

HTML WG, either based on the work of Community Groups, or based on proposal drafts created in

an HTML WG Task Force or the HTML WG itself.

* Ian will continue editing the WHATWG HTML specification, which we anticipate will be one such

proposal.

* Editors of Recommendation-Level specifications and authors of HTML.next proposals are

encouraged to work together to avoid introducing contradictions, but are free to make their own

changes directly.

* W3C has started the process of extending the W3C HTML WG charter to jump start the work on

HTML.Next in parallel to completing the current Recommendation track work. Once the HTML

WG is re-chartered then the W3C will review proposals for HTML.Next work, and seek additional

editors or co-editors for HTML.Next work.

* As W3C proceeds with its work on follow-ons to HTML 5, W3C and the WHATWG plan to continue

their partnership in developing the right features for the future web.

In July, the W3C’s new editorial team was announced, and now in 2013 it’s been expanded (with Ian Hickson still

listed as a participating editor).

So, by the W3C’s explanation, HTML5 needs to be standardized and set in stone. WHATWG is working on a living

standard that will never be finished, so the W3C needed to break away, take a snap shot, and lock down HTML5.

HTML development will continue as “HTML.next” (referred to as HTML5.1 by late 2013) and continue drawing

inspiration and ideas from the WHATWG specification.

In September 2013 the W3C gave itself a new charter for the HTML5 spec that lasts through July 2015, specifying

its license for distributing the HTML5 spec and redeclaring its intention to publish a formal and finished HTML5.0

specification in 2014 (www.w3.org/blog/news/archives/3253). None of this is mirrored by the WHATWG, though

Hickson’s involvement in both is intended to keep the two groups from diverging too far.

In the year since the W3C and WHATWG diverged, little has changed in the W3C spec. The W3C has focused on

breaking the single, large HTML5 spec proposed by the WHATWG into several smaller specs. Isolated differences have

emerged, but both the W3C and WHATWG, groups that are publishing specifications about how HTML5 should work,

frequently affirm that nothing matters until the browsers implement a feature. Let me say that again: in 2013, the W3C

Chapter 1 ■ a Somewhat SenSationalized hiStory of html5

and WHATWG are again working on different specifications, and both agree that only the browser makers’ decisions

really matter. See the following two URLs for more info:

http://html5doctor.com/interview-with-robin-berjon-html5-editor/

http://dev.w3.org/html5/decision-policy/html5-stabilization-plan.html

So, after all that, we’re back in a familiar place. The W3C has a group of editors working on a spec, the WHATWG

has an editor working on their spec, and the major browser companies are involved in both and implement whatever

they think works best. There’s more cooperation and commitment on all fronts this time, but it still feels eerily

familiar. We’re back to HTML.

That wraps up our somewhat sensationalized (and highly condensed) history of HTML5. Or HTML. Or . . . you get

the idea.

TL;DR

In summary, the W3C tried to kill HTML and took us on a decade-long journey to nowhere; some people from

browser vendors formed a group interested in web apps and evolving HTML’s forms; they worked outside the W3C

on what became HTML5; the W3C realized they were screwed and agreed to use their work; browser vendors are

implementing it (or their existing implementations of certain features have been standardized); web standards have

become a Microsoft marketing buzzword; hell has not frozen over.

What We’ll Be Focusing On

HTML5 is a massive specification, filled with mind-numbing detail for browser vendors.

But that detail is actually the best thing about it. Removing the implementation ambiguities has led to more

predictable behavior, which is good news for designers and developers alike. (Before that, browser vendors were

looking over each other’s shoulders to see how parts of the spec were interpreted.)

It’s not sexy work but rather years of careful documentation and clarification by the WHATWG that we can all be

grateful for.

The other parts of HTML5 very much reflect its origins as Web Applications 1.0 and Web Forms 2.0. We’ll touch

on the web app stuff in Chapter 12 and look at the web forms in Chapter 8.

As designers, the biggest point of interest are the changes and additions to the actual markup side of HTML.

And that’s what we’ll focus on: semantics, forms, graphics, and audio/video.

We’ll also touch on the new features for web apps in HTML5, which we’ll hopefully see in our content

management systems sooner rather than later.

Most importantly, though, we’ll be looking at the ideas in markup and the practical—sometimes critical—dos and

don’ts of HTML5 along the way.

Let’s jump in and look at how we start a document in HTML5.

Chapter 2 ■ the truth about a basiC htML5 Web page

There’s no need to specify type="text/css" or type="text/javascript" anymore—the browsers assume it anyway.

We can start using these techniques now. There’s no harm in them; they just make it simple enough to start

writing our documents from memory. (The old techniques will continue to work, though—probably forever.)

So, a basic HTML5 page (with basic body content) looks like this:

<!doctype html>

<head>

</head>

<body>

</body>

</html>

As you can see, it’s pretty much what we’re used to, just simpler.

Formatting Changes in HTML5

Here are a few things to note about how we write HTML in HTML5:

• Quotes are optional. You no longer need to quote attribute values, so you can write

HTML5 leaves it up to you.

• It’s case-insensitive. You can write your markup in upper or lowercase, or even in a mix like

<DiV ClAsS=VaLuE> if you really hate your co-workers and/or feel nostalgic for YoUr WaCkY

MySpAcE days.

• Closing slashes are optional. You no longer need to close stand-alone tags with a closing

slash (for example, <meta charset=utf-8 />). As you probably guessed, this was a relic of the

move to XML. Likewise, <br> and <br /> are both perfectly valid—it’s up to you.

If you’re a stickler for XHTML’s stricter syntax (always writing in lowercase, quoting attribute values, and closing

stand-alone tags), you can keep doing it—it will always be happily supported.

What About an HTML5 Shim and CSS for the New Elements?

HTML5 introduces new elements such as <nav>, <header>, <article>, <section>, and so on. These sound fine in

theory but are terrible in practice.

To support these elements in IE6–8, others suggest you include a small script that tells IE6–8 these elements exist

and to use whatever styles you specify for them (it will leave them unstyled otherwise). I don’t recommend using

these new elements, so we don’t need the HTML5 shim. (If you really want to use them, here’s the code to do it:

http://code.google.com/p/html5shiv/. But seriously, don’t use the new elements. You’ll thank me later.)

剩余183页未读，继续阅读

南风以南

粉丝: 429
资源: 40

HTML5真相：现在与未来

Drive The Surprising Truth About [epub]

The Whole Truth About Whole Numbers: An Elementary Introduction to Number Theory

The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

The truth value of a DataFrame is ambiguous.

The truth value of an array with more than one element is ambiguous咋办

The truth value of a Series is ambiguous

The truth value of an array with more than one element is ambiguous.

The truth value of a Index is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all().

ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

ValueError: The truth value of a DataFrame is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all()

The truth value of a series is ambiguous

The truth value of a Series is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all().

TDOA定位技术详解及其实现方法

matlab求数组长度《MD文档》

大学生职业生涯规划书Word模板范文就业求职简历应聘工作PPT物流专业

Python 实现GPR高斯过程回归多输入单输出回归预测（多指标评价）（包含详细的完整的程序和数据）

并行编程加速器：Fortran中的OpenMP深度解析《word文档》

2024嵌入式面试资料GCC中文手册2024嵌入式面试资料GCC中文手册

校园医疗保险管理系统 JAVA高分毕业设计 Vue.JS+SpringBoot前后端分离项目.zip

chan算法详细学习教程攻略 chan算法原理应用场景概述

最新资源