The pattern attribute for regular expressions looks like a great addition. Obligatory comment that "no more...server side code to check if the user's input is a valid email" is clearly a terrible advice. Always validate on the server.
Specifically, they've redefined the format of email addresses in a way that's much simpler and is actually amenable to regular expressions. "This requirement is a willful violation of RFC 5322, which defines a syntax for e-mail addresses that is simultaneously too strict (before the "@" character), too vague (after the "@" character), and too lax (allowing comments, whitespace characters, and quoted strings in manners unfamiliar to most users) to be of practical use here."
The spec even includes a Perl-compatible regex as an example. :)
[^ @]*@[^ @]*
[^ @]+@[^ @]+
^[^ @]+@[^ @]+$
That said, HTML5 has something even better if the input is expected to be an email address: input@type=email
See http://www.w3.org/TR/html-markup/input.email.html for more details.
dns-prefetch and prerender are not "HTML5". They're experimental/proposals from couple of browser vendors.
<link rel="dns-prefetch" href="//fonts.googleapis.com">
Also, a lot of the other bits aren't supported on IE 8/9 which is optimistically 1/3-1/2 the users on a lot of websites... it's worth doing, but doesn't mean you can/should forgo server-side checks/code. I find a lot of the client/server frameworks that are client-centric people are coming up with that do no input validation server-side to be more dangerous than a lot of older frameworks. It's like SQL injection issues all over again.
Edit: And I suddenly thought... for SSL pages would dns-prefetching leak some information to an observer about the composition pf content or the linked resources on a page by grouping such DNS requests into a short burst at the same time as the SSL request?
Last but not least, AFAIK, I'm not aware of any logic to group DNS-prefetch hints or similar strategies when running over TLS.
Can you tell me if it’s actually working from using the pagination at the bottom of the front page, or the pagination inside the permapages: http://pygm.us/1e9KHCYt. (Link fixed.)
And "yes": https://www.evernote.com/shard/s1/sh/0f3592b8-d72c-40f7-9bbf...
Thanks for the help, by the way. :)
I'm pleasantly surprised to find out it now works correctly on Firefox. It was Chrome only last time I checked.
client side validity checking is about the user experience, I mean if the user is doing something wrong you can guide them to the right direction without the need of server interaction and server interaction is always slower that one line of client side code.
Bounds checking and validation on the server will never go away...
And this is also somewhat amusing, since if I recall firefox has boasted 0 second reloads when you hit "back" fora long time now. Does chrome support that, yet?
Worth reading : https://developer.mozilla.org/en-US/docs/Link_prefetching_FA...
And... I believe I stand by my complaint regarding it.
That's because they aren't "HTML5" yet.
Download Attribute - http://caniuse.com/download
Datalist - http://caniuse.com/datalist
You'd also have the advantage of the article always being relevant.
Scroll down for list of browsers (and versions) that support prefetch / prerender / and other hints.
What it does is help the interface to be more responsive so the user doesn't have to wait for a round-trip before finding out that they forgot to put in an email address / other valid input.
<link rel="prefetch" href="http://davidwalsh.name/wp-content/themes/walshbook3/images/s... />
Oversights like these subsequently constrain other developments, such as the case for basing HTTP 2 on SRV records, using DANE to authenticate certificates and so forth.
1. upload something at http://html5-demos.appspot.com/static/dnd/all_types_of_impor...
2. see files list here filesystem:http://html5-demos.appspot.com/temporary/
as someone who worked with HTML5 FS API before, I can tell you its async API design ins PITA to write with.
There are some other limitations discussed here: http://msdn.microsoft.com/en-us/magazine/dn133614.aspx
To be honest, datalists are pretty worthless for every situation where I've needed to implement auto-complete functionality in projects, simply because the universe of possible entries has been always been huge.