W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2010

[whatwg] XSS safe templating

From: Henri Sivonen <hsivonen@iki.fi>
Date: Wed, 10 Mar 2010 06:38:12 -0800 (PST)
Message-ID: <213441389.35988.1268231892352.JavaMail.root@cm-mail03.mozilla.org>
"Mike Samuel" <mikesamuel at gmail.com> wrote:

> I'm working with EcmaScript TC39 trying to allow for experimentation
> with new content generation techniques in JavaScript.
> There's one missing piece which would let template language authors
> experiment with varying degrees of XSS-safety, and I was hoping that
> a
> change like the below might make it into HTML5.

Shouldn't XSS-safe templating use the DOM APIs to generate a tree (fragment) instead of trusting the built-in HTML parser of the browser to behave in a certain way?

> When user-code does
> ? ?document.write(value), myElement.innerHTML = value, etc.
> and the value is an object, currently it is coerced to a string by
> indirectly calling the toString method. ?I would like the toString
> method to be called with 'html ' + the current HTML 5 insertion mode
> to give structured template return values a chance to apply
> appropriate escaping schemes. ?For attribute sets, it would be nice
> to
> call toString with the argument 'attr ' + attribute name. ?This would
> be backwards compatible as toString implementations ignore parameters
> (modulo Number).

What would the object do with this information? Without knowing how you are planning on using this information and filling in the lack of information with my own guesses, my knee jerk reaction is very negative.

FWIW, in Gecko currently, the stringification happens a few abstraction layers away from the parser, so implementing your suggestion would involve punching holes in those abstractions.

-- 
Henri Sivonen
hsivonen at iki.fi
http://hsivonen.iki.fi/
Received on Wednesday, 10 March 2010 06:38:12 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:21 UTC