W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Fri, 1 Jun 2012 03:27:37 -0700
Message-ID: <CABNRm63MT0LGPYzXoc8W7vCFuM6cwh+jBJcAns5seiEB206mQQ@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Jonas Sicking <jonas@sicking.cc>, Rafael Weinstein <rafaelw@google.com>, Yehuda Katz <wycats@gmail.com>, Webapps WG <public-webapps@w3.org>, Scott González <scott.gonzalez@gmail.com>
On Thu, May 31, 2012 at 7:55 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
>  On Sat, May 19, 2012 at 6:29 AM, Ryosuke Niwa <rniwa@webkit.org> wrote:
> > There appears to be a consensus to use document.parse (which is fine with
> > me), so I would like to double-check which behavior we're picking. IMO,
> the
> > only sane choice is to unset the already-started flag since doing
> otherwise
> > implies script elements parsed by document.parse won't be executed when
> > inserted into a document.
> I was expecting document.parse() to make scripts unexecutable. Are
> there use cases for creating executable scripts using this facility?

jQuery appears to let script elements run: http://jsfiddle.net/kB8Fp/2/

Also, we're talking about using the same algorithm for template element.
I would like script elements inside my template to run.

- Ryosuke
Received on Friday, 1 June 2012 10:28:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC