Some of the most exciting enhancements coming in HTML5 are centered around the specifications made to improve online forms on the web. These new features have been "coming" for a long time now and we're here to share how you can use these new capabilities to improve your conversion rates and increase your bottom line. We'll look at and share some aggregate data on our end in addition to updating you on the current research and best practices that can come from using these new technologies.
Most people will know that this is new technology that isn't supported in all browsers. We'll cover how that's OK and what you need to do to design them around the ideas of progressive enhancement. We'll also cover how many of these features can use fallback technology to implement the same idea until all the browsers catch up. Particular attention will be paid to how mobile devices can benefit from these new features perhaps even more so than desktop browsers.
The technical aspects of using the new features of HTML5 forms will be covered after it is made clear why using that feature is a good idea. New features include:
The term HTML5 now refers to the much-hyped kitchen sink of the web. It covers *everything* including things not officially part of the HTML5 specification. Yet "HTML5" is now the catch phrase to describe the new wave of platform competition on the web, and browser vendors vie to outdo each other on benchmark tests touting compliance and performance.
Every major browser vendor -- Apple, Opera, IE, Chrome, and Firefox -- will have a significant browser release by SxSW 2011. Microsoft's recent IE9 press event suggests that they are "all in for HTML5." So if all of us browser vendors are "all in" for HTML5, what does this mean for web developers? And what's up with the dirty marketing buzz around tests and demo pages?
This panel will expose the areas where we browser vendors cooperate as well as compete, and will push on the painful spots where we seem to disagree. We'll bring every major browser vendor to the table, and talk about open video on the web (and video codecs), what this all means to Flash, APIs (including contentious ones, like databases), CSS (including once hot areas like fonts) graphics, SVG vs. Canvas, WebGL, Device APIs, and security.
This browser wars panel will be less like Inside Baseball, and more about the practical issues confronting web developers today. We'll poke at the raw spots that browser vendors need to discuss. As always, audience participation will account for a substantial chunk of time.
11th–15th March 2011