PUBLIC MARKS with tags browser & html5

Kaazing products power the Living Web – the dynamic, real-time, interactive, collaborative online world that has organically evolved into the norm. Building on the HTML5 WebSocket standard and extending WebSocket functionality to any browser or protocol, Kaazing products enable instantaneous, full-duplex delivery of content back and forth between any browser or mobile device and any backend service. The Kaazing product family is built on the Kaazing Platform, which provides a unified architecture for write once, use everywhere application development that can save vast amounts of both time and money in developing and deploying Rich Internet Applications. Whether exchanging content with mobile devices, browsers or other servers, the Kaazing Platform delivers the highest scalability, security and performance available in the market today.

Übersicht über Skripte die Browserschwächen ausgleichen MMM

So here we're collecting all the shims, fallbacks, and polyfills in order to implant html5 functionality in browsers that don't natively support them. The general idea is that: we, as developers, should be able to develop with the HTML5 apis, and scripts can create the methods and objects that should exist. Developing in this future-proof way means as users upgrade, your code doesn't have to change but users will move to the better, native experience cleanly.

A web workers tutorial, for implementing a Twitter fall in a web page.

A straight and simple howto of client-side forms validation in Firefox 4.

Parmi la montagne de spécifications du standard en devenir HTML5, on trouve le protocole WebSocket. Toutes les versions en développement des navigateurs intègrent son support, mais la situation vient de brutalement s’inverser : des failles de sécurité ont été trouvées dans le protocole, et des éditeurs font machine arrière.

"You may well ask: “How can I start using HTML5 if older browsers don’t support it?” But the question itself is misleading. HTML5 is not one big thing; it is a collection of individual features. So you can’t detect “HTML5 support,” because that doesn’t make any sense. But you can detect support for individual features, like canvas, video, or geolocation."

Version 1.1 fills in some of the gaps by testing for more exciting HTML5 features like localStorage, Web Workers, applicationCache and more…

Démonstration et comparatif du support des fonctionnalités HTML5.

The emerging HTML5 specification lifts video playback out of the generic object element and into specialized video handlers. Explicit markup for audio and video places elevates moving pictures to a similar native rendering capacity as img markup we are used to but with more fine-grained details about underlying formats and compression available before loading. In this post I will dive into implementation details of HTML5 video based on currently available consuming agents and outline some of the nuances of preparing media for playback.