HTML and CSS

Facebook Twitter
About Font Embedding
Mozilla moves to H.264 Feature By Daniel Eran Dilger Mozilla's director of research Andreas Gal has proposed enabling mobile H.264 video decoding via hardware or the underlying operating system, signaling the end to the group's war on the Apple-led H.264 video codec. The move is necessitated by the overall lack of support for Google's WebM video codec, which Mozilla and Google hoped would replace H.264, the technology backed by Apple, Microsoft, Nokia and other commercial vendors. Mozilla moves to H.264

HTML5

HTML5 Shared Links is the best way to see what’s up on the web. When you’re in the mood to read something new, quirky, or cool, open Shared Links in the Safari Sidebar, where you can view links from people you follow on Twitter and LinkedIn. You can scroll seamlessly from one story to the next, no clicking required.
December 08, 2010 Follow @peterwayner The five characters HTML5 are now an established buzzword, found everywhere on the Web and often given top billing in slides, feature lists, and other places where terms du jour congregate. HTML5 in the browser: Canvas, video, audio, and graphics | Application Development HTML5 in the browser: Canvas, video, audio, and graphics | Application Development
HTML5 in the browser: Local data storage | Application Development HTML5 in the browser: Local data storage | Application Development Of all the changes bundled in the HTML5 drafts, few are as radical or subversive as the options for storing data locally. From the very beginning, the Web browser was intended to be a client in the purest sense of the word. It would display information it downloaded from a distant server, and it would do everything the distant server would tell it to do.
HTML5 in the browser: HTML5 data communications | Application Development HTML5 in the browser: HTML5 data communications | Application Development From the beginning, Web users have had mixed feelings about the way their browser communicates. On one hand, the idea of a tightly controlled sandbox is appealing because it limits the damage a website may do to our personal data and to the Web as a whole. Without these controls, just clicking on a link could unleash viruses, worms, and worse. On the other hand, programmers have always complained about the browser's restrictions, pointing out the ways they limit the services that might be made available. Every AJAX developer can easily identify one way they could make their code that much cooler and more awesome if only the browser would loosen the rules governing the sandbox, but just this once and only for their code.
March 09, 2011 Follow @peterwayner The changes and enhancements to the form tags are some of the most extensive amendments to the HTML5 standard, offering a wide variety of options that once required add-on libraries and a fair amount of tweaking. All of the hard work that went into building self-checking widgets and the libraries that ensure the data is of the correct format is now being poured into the browser itself. The libraries won't be necessary -- in theory -- because the work will be done seamlessly by all browsers that follow the standard. In practice, we'll probably continue to use small libraries that smooth over slight inconsistencies. HTML5 in the Web browser: HTML5 forms | Application Development HTML5 in the Web browser: HTML5 forms | Application Development