《What HTML5 is (and what it isn't)》 -----本字幕由ACELY 整理制作----- Before we began exploring HTML5 in more detail, it's worth taking a moment to
【如果喜欢该教程，请购买正版！】 discuss what HTML5 actually is, as opposed to what the current hype machine is defining it as.
【----ACELY STUDIO----】 【作品只能交流学习，不得用于任何商业盈利用途】 Now, I suspect I'm fighting a losing battle here because the current state of
affairs seems to be taking any relatively new feature or a cool browser trick
and slapping the HTML5 label on it.
Now recently, Apple launched its HTML5 Showcase page, featuring six really
cool demos of features like transitions, next-generation typography, and video support.
The only problem was that only two of the examples featured HTML5 capabilities,
the audio and video demos.
The rest were collection of CSS3, JavaScript, and Safari-only CSS extensions.
Now while stunning, they weren't strictly HTML5.
Now I'm not just picking on Apple.
It seems like every tech blog, publication, or demo site out there can't wait to
throw the HTML5 label on any new browser capability or web application
technique they come across.
In a now famous post on his blog Software As She's Developed, Michael Mahemoff
declared that HTML5 has now become a brand, representing a new type of web
application rather than the specification itself.
I think he has a point.
Now in the overall scheme of things, how the term HTML5 is co-opted as a
marketing tool really isn't that important.
As a guide for learning HTML5, it's very important that you understand the difference.
Now, it's not uncommon for example, to hear CSS transitions, web sockets
geolocation, SVG and @font-face mentioned under the HTML5 banner.
Now if you go poking through the HTML5 specification, you won't find a trace of them.
That's because they either belong to the CSS3 specification or other API
specifications within the World Wide Web Consortium.
Well it's clear that future web sites and applications will be built using on
combination of HTML5, next-generation APIs, JavaScript and CSS3, as a designer
or developer you need a clear understanding of each of these technologies, and
how they fit together.
Something that's getting a little harder to do the more the term HTML5 becomes confused.
Now, perhaps the most alarming trend recently has been the introduction of
browser proprietary features that are then labeled under web standards.
Mozilla, Opera, and WebKit, all feature proprietary CSS properties that require
web designers to write much more complex code to achieve cross-browser results.
While some of these are the results of specific browsers wanting to implement
standards that aren't finished yet, many are motivated by the desire to gain an
edge in the increasingly competitive browser field.
Now this type of behavior isn't limited to CSS either.
Apple's native video support in Safari supports QuickTime movie files when
QuickTime is installed and uses a proprietary technology for streaming video.
Now, anybody can admire the quality of these features but Apple lists them in
their support of web standards in HTML5.
Although they are restricted to the Safari Browser. So what is HTML5?
Well, using a strict definition, it's a continuation of previous HTML
specifications in the DOM Level 2, designed to address how modern web
applications are created.
There are enhancements to syntax and semantics, the deprecation of presentational
elements, and formal definitions for many of the APIs that form the foundation of
most web applications.
Now these include video, audio, dragging and dropping, offline applications, and canvas.
So if we step back a bit, it gives us a broader perspective that HTML5 is
focused on creating a consistent browsing experience and in turning the browser
into more of an actual application platform.
If adopted by user agents, designers, and developers, it should represent a
significant evolution in the future of the web.
On the other hand, if the term becomes co-opted and used to label proprietary or
unrelated technology, we could find ourselves in a situation very similar to
what we had in the late 90s where designers often had to create multiple
versions of sites to work across multiple browsers.
-----本字幕由ACELY 整理制作----- -----欢迎加入群号：214645753----- Now that's why understanding what HTML5 is and then supporting the resulting
standards is an important part of determining how future web applications will be built.