Comments on: HTML5 Web Forms & Browser Support

By: How To Make Forms More Usable With HTML5 | Van SEO Design

How To Make Forms More Usable With HTML5 | Van SEO Design — Mon, 28 Nov 2011 13:31:33 +0000

[...] browser support isn’t all that good with these new inputs, however in most cases the fallback is a text box. [...]

By: JS Variable Scope, HTML5 Web Forms | Suyok's Blog

JS Variable Scope, HTML5 Web Forms | Suyok's Blog — Sun, 13 Nov 2011 05:52:36 +0000

[...] HTML5 Web Forms and Browser Support [...]

By: New Browser Releases: Opera 10.6 and Firefox 4beta | Suyok's Blog

New Browser Releases: Opera 10.6 and Firefox 4beta | Suyok's Blog — Sun, 13 Nov 2011 05:52:15 +0000

[...] support for web video, audio, and drag & drop, there has been precious little improvement in Web Forms support. Similar to Safari 5, the beta release has removed some support from :link and :visited. In Ã¼ber [...]

By: Using HTML5 Now « Temperies Blog

Using HTML5 Now « Temperies Blog — Wed, 06 Jul 2011 15:07:52 +0000

[...] One of the aspects that have been greatly improved in HTML5 are the forms, including new input types , new form elements and some new form and input attributes. As with the previous elements that we have seen the main problem is adoption and the older browsers. [...]

By: HTML5 Forms: browsers get jetpacks « Two Banjos At Once: The Blog

HTML5 Forms: browsers get jetpacks « Two Banjos At Once: The Blog — Thu, 09 Jun 2011 21:06:05 +0000

[...] standardista Estelle Weyl enlivened a recent HTML5 Meetup with her summary of the neat stuff we could use if only everybody used, say, the latest version of [...]

By: Estelle Weyl

Estelle Weyl — Sat, 19 Jun 2010 21:34:07 +0000

You’re likely right. I haven’t finished this post… am halfway done with the new types. It is right up to what is detailed below. If you see the note “Note: this is as far as i’ve gotten at this point on explaining web forms. I do plan on coming back and revisiting this page in June 2010 to update.”, that’s up to where i have thoroughly tested. I should probably put that in bold. My sandbox is http://www.standardista.com/sandbox/html5formelements.html … that file is a test page and is constantly changing.

By: Colin Snover

Colin Snover — Thu, 17 Jun 2010 03:35:06 +0000

Hi,

Not sure how you did your testing here, but my tests show that Firefox 3.6 and all versions of IE do not support the maxlength property on s, which makes me suspect that some of your other tests are not valid as well. Hope you can get it all fixed up, since it would be great to have a single resource to go to for HTML5 forms support.</p> <p>Regards,</p> </article> <article> <h1>By: Philippe Le Hegaret</h1> <p>Philippe Le Hegaret — Wed, 19 May 2010 00:08:56 +0000</p> <p>Your description of how FIELDSET is displayed is not standard. The FIELDSET element allows authors to group thematically related controls and labels. How that is presented to the user, whether visually or otherwise, is not specified (nor should it be).</p> <p>You wrote: “‘disabled’ in IE6 and Opera disables all form elements within the fieldset. In IE7 and IE8, the attribute only disables form elements in the . ”</p> <p>In IE versions, the disabled property can be used to disable arbitrary elements. See MSDN:</p> <p><a href="http://msdn.microsoft.com/en-us/library/ms533732%28VS.85%29.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms533732%28VS.85%29.aspx</a></p> <p>We can test the behavior can seen on a FIELDSET with FORM. The behavior is identical.</p> <p>In IE:<br /> javascript: void(document.forms[0].disabled = true);</p> <p>- do the nested form controls look greyed out in IE? Are they disabled or does they just look like it because the form is disabled? Did you try interacting with the controls? </p> <p>Your readers may be assured that the controls can still be interacted with.</p> </article> </main></body></html>