> Also, look up HTML imports using LINK element. Works well with scoped stylesheets. Thanks for the suggestion. Right now I'm just concerned with the mechanics of script data blocks, but like <template>, HTML imports is also a useful tool. Thanks, Jesse ----- Original Message ----- From: "Garrett Smith" <dhtmlkitchen@gmail.com> To: "Ian Hickson" <ian@hixie.ch> Cc: "Jesse McCarthy" <whatwg-2010-04@jessemccarthy.net>; <whatwg@whatwg.org> Sent: Friday, November 07, 2014 3:52 PM Subject: Re: [whatwg] <script> content restrictions vis-a-vis HTML template data blocks > On 11/7/14, Ian Hickson <ian@hixie.ch> wrote: >> On Wed, 5 Nov 2014, Jesse McCarthy wrote: >>> >>> Re: the "Restrictions for contents of script elements" (4.12.1.2): >>> >>> Consider <script> elements containing data blocks. It's useful to embed >>> templates in these; HTML templates for example. When embedding HTML >>> templates, >>> it would be onerous to have to either omit comments or implement an >>> escaping / >>> unescaping regimen. >> >> Have you considered using the <template> element? >> >> > Also, look up HTML imports using LINK element. Works well with scoped > stylesheets. > -- > Garrett > @xkit > ChordCycles.com > garretts.github.ioReceived on Tuesday, 11 November 2014 00:35:19 UTC
This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:26 UTC