This has been an interesting week for the web design community, to say the least. The W3C revealed a new HTML5 logo to help designers and developers ‘tell the world’ that they’re using HTML5. The logo was designed by Ocupop design agency, and it’s licensed under Creative Commons Attribution 3.0, a permissive license that allows ‘remixing’ of the licensed work. The logo has been made available on stickers and t-shirts, and there’s a gallery already promoting examples of the logo in use.
The logo’s official site includes a “badge builder” that customizes its orientation and allows you to add supplementary icons to indicate support for the different technologies that have become associated with HTML5.
One of things that we need to get used to when making the switch from HTML4/XHTML to HTML5 is the way HTML5 validation works, because it’s drastically different from what we’ve become accustomed to in previous iterations of web markup.
First, it should be noted that the W3C’s HTML5 validation engine is “experimental”, so it’s a work in progress that will likely see many changes over the next year or more. Also, we shouldn’t refer to it as a “validator” anymore; it’s now more accurately referred to as a “conformance checker” (although for simplicity I’ll be using the term “validation” and its derivatives).
One of the pieces of functionality commonly discussed when distinguishing HTML5 from previous versions of HTML is the standardization of geolocation via the Geolocation API. Although some browsers supported geolocation functionality prior to HTML5, it is the standardized API that brings new value. This is true of many aspects of HTML5 where HTML5 standardizes across compliant browsers what formerly required browser-specific extensions. The geolocation standardization process is not technically part of the HTML5 specification [it is its own World Wide Web Consortium(W3C) specification], but its timing makes it easy to lump in with other HTML5 enhancements. In other words, it is “HTML5″ in the larger sense of “next generation HTML” as opposed to strict HTML5 as outlined in the specification.
how do we get a video to play in HTML? First you need an actual video in the right format. Opera supports Ogg/Theora/Vorbis, which is also supported by Firefox and Chrome.
If you have a video around you want to play but it’s not in Ogg/Theora/Vorbis, you need to convert it. You can use Firefogg or ffmpeg2theora or other programs to do this; Dive into HTML5 is an online book which covers how to do this step-by-step. It also covers how to convert to MPEG-4/H.264/AAC.
So now you have a video lying around on your server (or your local disk), and you want to play it in HTML. Use the following markup:
< video src="video.ogv" controls >
video not supported
< /video >The controls attribute instructs the browser to provide its own controls. If you want to write your own controls with JavaScript, you just leave out the controls attribute. The browser’s controls can still be enabled by the user from the context menu in Opera, and when scripting is disabled, Opera’s controls are present regardless of the controls attribute.
Ready to see how much you learned from HTML5 and CSS3 for the Real World? Complete this short quiz.
HTML5 is being developed as the next major version of HTML. This Code can used for new functions that can benefit developers and internet users.
HTML5 introduces number of new elements and attributes. Here are most important of them
Geolocation
Sniffing users location is not a new thing on the web. Infact most website already do this by IP address detection, but its not reliable. So HTML5′s Geolocation is an alternate method of correctly pinpointing a user’s location. The new idea is to get the location information from Wifi towers and GPS.
Offline Web Applications
The Offline Web Applications enable users continue interacting with web applications and documents even when there network connection is unavaialble. The user can, for instance, can access email locally without having to connect to the internet or install an extenal client
Using CSS to give text a visually bold appearance and using < strong > to give text more emphasis (for SEO or overall content strategy) was the correct way. In HTML5 things are similar but slightly different. Now, according to the spec, the < b > element is used to make text “stylistically offset from the normal prose without conveying any extra importance.” So it no longer means “make this bold”. Technically, the letter “b” used in the element has nothing to do with “bold” anymore. You can use < b > for key words, the lead sentence in an article (the spec uses this BBC article as an example), or other text that should stand out from the rest, but that you don’t want to have extra importance.
We came over 15 demos of the HTML5 capability. They all seem great, we’ve been impressed by each of them. Which one is your favourite?
Muglia’s response was pretty telling. Although he reaffirmed Microsoft’s commitment to making Silverlight the development platform for Windows Phone, he noted that the cross-platform solution Microsoft sees going forward is HTML.
Speaking with Foley, Muglia said, “HTML is the only true cross platform solution for everything, including (Apple’s) iOS platform.”
All the while, Microsoft is increasingly embracing HTML5. The company’s recent launch of Internet Explorer 9 beta was promoted using a number of different HTML5-specific web pages and promotions. Silverlight may not have been mentioned much during PDC, but HTML5 certainly was.
Microsoft’s new IE9 web browser (which is in public beta testing) will be a big part of this strategy. And presumably, a lot of the things that currently require Silverlight, like some of those nifty Bing Maps features, will move to HTML5 going forward. Again, that’s great news.
So why is Microsoft doing this? It seems that Microsoft sees the writing on the wall. They likely know that’s it’s going to be much harder to make a dent in the new developer world order with Silverlight, which still has a relatively small market penetration and no penetration in mobile, than with HTML5, which is (or shortly will be) everywhere — including all of Apple’s devices.
“HTML is the only true cross platform solution for everything, including (Apple’s) iOS platform,” Muglia told Foley.