- From: Brendan Eich <brendan@secure.meer.net>
- Date: Thu, 14 Mar 2013 17:42:37 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: Mike Samuel <mikesamuel@gmail.com>, Ian Hickson <ian@hixie.ch>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Adam Barth <w3c@adambarth.com>
You guys should give it up -- E4H ain't going anywhere. Sorry. /be Tab Atkins Jr. wrote: > On Thu, Mar 14, 2013 at 5:16 PM, Brendan Eich<brendan@secure.meer.net> wrote: >> Right, I keep forgetting (and apols to Hixie for assuming E4H used a full >> HTML parser). >> >> However, for template strings the holes contain the results of evaluating >> arbitrary expressions. The html`...` handler would validate the results that >> fill each hole but only at runtime, of course. > > Yes, a more normal html template handler would have more arbitrary > constraints, and could fail at runtime. I (and Hixie) are only > referring to E4H, whether invoked with dedicated JS syntax or as a > built-in handler. > > ~TJ >
Received on Friday, 15 March 2013 00:43:04 UTC