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().
On Tue, Jun 5, 2012 at 12:58 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jun 5, 2012 at 2:10 AM, Adam Barth w...@adambarth.com wrote:
Doesn't e4h have the same security problems as e4x?
If you mean http://code.google.com/p/doctype-mirror/wiki/ArticleE4XSecurity
I guess that would
On Tue, Jun 5, 2012 at 2:10 AM, Adam Barth w...@adambarth.com wrote:
Doesn't e4h have the same security problems as e4x?
If you mean http://code.google.com/p/doctype-mirror/wiki/ArticleE4XSecurity
I guess that would depend on how we define it.
A (bigger?) problem with E4H/H4E is that TC39 does
On Tue, Jun 5, 2012 at 11:02 AM, Adam Barth w...@adambarth.com wrote:
On Tue, Jun 5, 2012 at 2:10 AM, Adam Barth w...@adambarth.com wrote:
If you mean http://code.google.com/p/doctype-mirror/wiki/ArticleE4XSecurity
I guess that would depend on how we define it.
By the way, it occurs to me
On Mon, 4 Jun 2012, Adam Barth wrote:
� http://www.hixie.ch/specs/e4h/strawman
Who wants to be first to implement it?
Doesn't e4h have the same security problems as e4x?
As written it did, yes (specifically, if you can inject content into an
XML file you can cause it to run JS under
On Fri, 25 May 2012, Rafael Weinstein wrote:
Now's the time to raise objections to UA's adding support for this
feature.
For the record, I very much object to Document.parse(). I think it's a
terrible API. We should IMHO resolve the use case of generate a DOM tree
from script using a much
Just to be clear: what you are objecting to is the addition of formal
API for this.
You're generally supportive of adding a template element whose
contents would parse the way we're discussing here -- and given that,
a webdev could trivially polyfil Document.parse().
I.e. you're ok with the
On Mon, 4 Jun 2012, Rafael Weinstein wrote:
Just to be clear: what you are objecting to is the addition of formal
API for this.
You're generally supportive of adding a template element whose
contents would parse the way we're discussing here -- and given that, a
webdev could trivially
On Mon, Jun 4, 2012 at 4:38 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 4 Jun 2012, Rafael Weinstein wrote:
Just to be clear: what you are objecting to is the addition of formal
API for this.
You're generally supportive of adding a template element whose
contents would parse the way we're
On Fri, 25 May 2012 09:01:43 +0200, Rafael Weinstein rafa...@google.com
wrote:
Ok, so from consensus on earlier threads, here's the full API
semantics.
Now's the time to raise objections to UA's adding support for this
feature.
-
1) The Document interface is extended to include a
On Fri, May 25, 2012 at 12:32 AM, Simon Pieters sim...@opera.com wrote:
On Fri, 25 May 2012 09:01:43 +0200, Rafael Weinstein rafa...@google.com
wrote:
Ok, so from consensus on earlier threads, here's the full API semantics.
Now's the time to raise objections to UA's adding support for this
On Fri, May 25, 2012 at 3:01 AM, Rafael Weinstein rafa...@google.comwrote:
-if start tag is td or td
typo: th
12 matches
Mail list logo
