Comments on: A third way to write and validate forms – HTML5

By: Patty

Patty — Thu, 30 Sep 2010 09:41:44 +0000

It’s perfect! Exactly what I was looking for, thanks so much for making it easy to understand and use

@Lucica: I think it’s important to explain to your clients briefly what’s going on with browsers and insist on how their internet navigation would be enhanced if they tried several browsers before making a final decision, I’m sure they’ll quickly adopt different browsers. I found that if people don’t know they have the choice, then they stick to what they know.

I have the same shared feeling regarding much modern design and coding tools, so I think it depends on what you do, on your target niche: geeks or grannies (it’s a shortcut for my idea, heh, I have nothing against grannies)? Then you decide if you REALLY have to bother about IE6 fixing issues etc.

Ultimately, you can’t please all browsers so it’s the target niche that counts )

I bookmark this site, I really like what’s going on here! xD

-Laters

By: CSS Brigit | A third way to write and validate forms - HTML5

CSS Brigit | A third way to write and validate forms - HTML5 — Wed, 05 Aug 2009 23:35:15 +0000

A third way to write and validate forms – HTML5…

HTML5 clientside forms validation. No javascript required.
This is a future to be implemented feature of browsers, but for Opera is working. Take a look at the simplicity and painless – no js – implementation.

…

By: Lucica Ibanescu

Lucica Ibanescu — Wed, 05 Aug 2009 16:19:26 +0000

Hi Jason, you are perfectly right and this is an on going fight since …well…forever, I guess. There’s no point in complaining about this, I have the feeling that MS will not listen (if they would, IE8 might have been a bit better, don’t you think?) and after I wrote this I was thinking if I should start embedding HTML5 & CSS3 in my projects – I have mixed feelings.

Altough it would be great for me (I learn) and for some users (with better browsers – altough they will not detect the improvements at a browsing level) I still think it’s not profitable from a financial point of view. Because that means I have to spend a lot of time trying to find JS scripts that would fix the layout in older browsers. And that will be very time consuming besides the fact that my clients will not “understand” my attempt to apply new technologies in their websites. (I know I’m evil for saying that, but we do not code for free)

And I definitely would not like to exclude IE users from browsing my sites nor do they deserve a lower browsing experience just because they are using the “bad” browser. So I think I’ll just asimiliate these news bit by bit and keep on checking my awstats to see what will happen in the next 6-12 months.

I’m really curious what other coders think about this.

By: Jason

Jason — Wed, 05 Aug 2009 15:42:53 +0000

I would love to see this fully implemented, it’s just such a shame that trying to update anything on the code end of the web is such a lengthy process… by the time this is finally approved and used across all (at whatever point in time this ends up being) modern browsers, we’ll be trying to get the new wave of tags and elements going. I know it’s been talked about and we’ve all heard both sides, but browsers and their manufacturers need a better way of releasing updates and ensuring that all of their users receive them in a timely manner so that the future of the web isn’t stuck years behind the present.