On Fri, 15 Jun 2012 14:21:09 +0200, Glenn Maynard wrote:
On Fri, Jun 15, 2012 at 12:05 AM, Charles McCathieNevile
wrote:
The reason for using it was in part that there were people there who
were
working on dom and not on the (quite high traffic) webapps list which
discusses many other thing
The blog article link has changed to:
http://blog.alexmaccaw.com/preview/Pc1LYBw4xDT95OPWZGihod7z8WhrnfAdXMjQxMDg3MTc5NDIaXNjA1p
A few people have raised (rightfully) security considerations. From the
article:
Getting the security considerations right is key to making this work. As
browsers alrea
I've been working on a way of integrating one-click payments (and signup)
into the browser, and I wanted to put it in front of a few people to get
some feedback.
The API I was playing about with was pretty simple, and is documented here:
http://blog.alexmaccaw.com/preview/MjQxMDcwOTcwNjAYz14YvbdZ
E4H doesn't address all the use cases of Document.parse().
It doesn't solve the problem of existing templating libraries
constructing DOM fragments from processed templates.
E4H (or something similar) would be great, but I think it's a mistake
to make it mutually exclusive with Document.parse().
