Expanding Images using HTML5′s contenteditable tabindex HTML5 has a new attribute, contenteditable, which can be applied to any element which allows it to be edited directly in the browser window. Think of text input with a predefined value, but it can literally be any element. Form elements like text inputs support the :focus pseudo class, which allow us to style those elements when they are clicked upon or otherwise navigated to. Giving an element the contenteditable attribute means it also now supports the :focus pseudo class, which opens up some interesting possibilities! We'll exploit this little trick to make an expanding image (like a lightbox without the overlay) right within some content. UPDATE: Even better, you can give attributes a tabindex attribute, like you would a form element, which allow allows :focus without the editability. HTML5 Markup HTML5 has nice elements for including captioned images. <section class="image-gallery"><figure><img src="images/img-1.jpg" alt="jump, matey" /><figcaption">Jump! The Images The CSS Related
Real Time Web Traffic Visualizer: Hummingbird HTML5 A vocabulary and associated APIs for HTML and XHTML W3C Working Draft 4 March 2010 This Version: Latest Published Version: Latest Editor's Draft: Previous Versions: Editors: Ian Hickson, Google, Inc. David Hyatt, Apple, Inc. This specification is available in the following formats: single page HTML, multipage HTML. Copyright © 2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. Abstract This specification defines the 5th major revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). Status of This document This section describes the status of this document at the time of its publication. E-mail notifications of changes Table of Contents
Plan B: Font Fallbacks « coding@scribd This is the fourth post in our series about Scribd’s HTML5 conversion. The whole process is neatly summarized in the following flowchart: In our previous post we wrote about how we encode glyph polygons from various document formats into browser fonts. We described how an arbitrary typeface from a document can be sanitized and converted to a so called “@font-face”- a font that browsers can display. The next challenge the aspiring HTML5 engineer faces is if even after hand-crafting a @font-face (including self-intersecting all the font polygons and throwing together all the required .ttf, .eot and .svg files ), a browser still refuses to render the font. After all, there still are browsers out there that just don’t support custom fonts- most importantly, mobile devices like Google’s Android, or e-book readers like Amazon’s Kindle. Luckily enough, HTML has for ages had a syntax for specifying font fallbacks in case a @font-face (or, for that matter, a system font) can’t be displayed:
Une vitrine HTML5 on the way... - Fatras - HTML5/CSS3 et autres Merci de me lire. Merci de commenter les billets. Merci de me témoigner vos encouragements. C'est très plaisant. Quand j'ai démarré ce blog, il y a 5 mois, c'était avec l'idée de rester dans mon coin à soliloquer sur mes turpitudes dans le monde merveilleux d'HTML5. Et voilà que je ne suis plus tout à fait seul. Ce weekend je vais bosser pour offrir une meilleure visibilité sur le Web à certains webmestres/codeurs/CSS designers/référenceurs/etc. qui s'intéressent à HTML5. Cette nouvelle catégorie ne sera pas un annuaire automatique : l'inscription sera manuelle. Le titre de la page : il figurera en H1 comme pour tous les articles. Il y aura un système de votes pour indiquer l'appréciation générale de votre site par les visiteurs. Je n'aurai certainement pas fini ce weekend mais dans la décade qui va suivre vous découvrirez la vitrine avec 2 ou 3 sites d'amis ou de relations que je veux promouvoir. Ah !
How HTML5 will change the Web | Developer World Many folks who are just tuning into the HTML5 saga because of the battle between Adobe and Apple are surprised to learn that the push to create a fifth official version of the HTML specification began six years ago. And that's just the first half of the story because the latest implementations, while nice, are far from standards. The HTML5 demos from Apple, for instance, are impressive, but they only run well on Safari. That's how slowly committees can work. While the jokes may sting and waiting for more general adoption is tiresome, it would be a mistake to simply ignore HTML5. [ Also on InfoWorld: Despite HTML5, Web designers have good reasons to cling to Flash for rich Web content. HTML5 will change many aspects of life on the Web. To see where this new standard may take us, I collected the opinions from a number of developers, programmers, and designers.
location.hash is dead. Long live HTML5 pushState! For a long time, location.hash was a way for AJAX applications to get back button and bookmarking support, and libraries like jQuery BBQ from Ben Alman made dealing with it cross browser a cinch. Now, with HTML5 coming of age, there is a new feature that aims to replace the use of location.hash with a better solution: pushState. Over on the Spoiled Milk blog, Jamie Appleseed describes the API as “a way to change the URL displayed in the browser through JavaScript without reloading the page.” window.history.pushState(data, "Title", "/new-url"); The last argument is the new URL. In order to support the back and forward buttons you must be notified when they are clicked. Currently, pushState has support from the latest versions of Safari and Chrome, and Firefox 4 will be supporting it as well. If you’d like to read a more in depth overview of these new features, you should check out the aforementioned blog post by Jamie Appleseed.
HTML5: The Basics (1 of 4) The next iteration of HTML has been met with excitement by some, loathing by others and confusion/fear by everyone else. Love it or hate it, HTML 5 will soon define how you build websites. This is the first article in a four part series that will introduce HTML5 and its basic features as well as explain the key differences from HTML4.01 and XHTML 1.0 so you can start preparing yourself and your sites for the transition. Over the next week we’ll be focusing on three major areas: 1. This article will briefly introduce each of these topics to prepare you for the in-depth articles ahead. APIs Before we dive into the topics listed above, I want to take a minute to look at an extremely important feature that we won’t be covering in its own dedicated article: the new APIs. As you can see, the principal purpose of these APIs is to facilitate web application creation. New Elements in HTML5 HTML5 introduces quite a few new elements. Semantic Changes 1. Getting HTML5 Working Today Conclusion
Dive Into HTML5 The Future of Web Apps - Single Page Applications | The Worm Hole The Future of Web Apps – Single Page Applications Mark Boas The world wide web is constantly evolving and so is the way we write the applications that run upon it. Due to differing paradigms we are forced to design our web apps in a completely different way to native apps. The price is high. In this article I propose that we can have our cake and eat it. But first let’s take a look at the advantages of a single-page approach. 1. What we are essentially talking about here is having an application where ‘virtual pages’ are loaded into one single web-page, which means switching between pages need not involve a trip to the server and so the switch occurs almost instantly. 2. Using the ‘traditional’ approach we load a lot of duplicated content for each page we visit. 3. When all ‘pages’ are accessible from one page you give yourself more freedom to manipulate the content of these ‘pages’ client-side. Making it Work Next let’s take a look at the example application. Try the Demo 2. 3. With me?