W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2012

Re: [whatwg] runat (or "server") attribute

From: Alexandre Morgaut <Alexandre.Morgaut@4d.com>
Date: Tue, 22 May 2012 19:27:18 +0200
To: Brett Zamir <brettz9@yahoo.com>
Message-ID: <972EE299-4C2C-405F-8FFE-0CB73B6C15FC@4d.com>
Cc: whatwg <whatwg@whatwg.org>

When we started developing Wakanda, a member of the team asked if it would be revelent to support the "runat" attribute in the script tag

It is supported by ASP, and Aptana Jaxer choose to support it as well
(Note: even PHP support it)

We rejected it

Such feature is a bad incitation  for the developer to mix its server-side code in what is meant to be the view
We never embed any JavaScript code in the HTML, we always put it in separate JS files

If one wants to generate HTML from server-side JavaScript, we recommend to use a template engine like mustache.js or pure (many others exist)

On 13 mai 2012, at 02:47, Brett Zamir wrote:

> Hi,
> With Server-Side JavaScript taking off, could we reserve "runat" (or
> maybe an even simpler and more concise "server" boolean attribute) for a
> standard and (via CommonJS) potentially portable way for server-side
> files to be created (and discourage use of HTML-unfriendly and
> syntax-highlighter-unaware processing instructions)?
> I know in the past Ian has showed a lack of interest in tending to HTML
> in other contexts (e.g., in rejecting a common include syntax), but
> could we at least lay this simple foundation for encouraging server-side
> portability (in a way that works well with existing syntax highlighters)?
> Thanks,
> Brett

Alexandre Morgaut
Wakanda Community Manager

60, rue d'Alsace
92110 Clichy

Standard : +33 1 40 87 92 00
Email :    Alexandre.Morgaut@4d.com
Web :      www.4D.com
Received on Tuesday, 22 May 2012 17:28:45 UTC

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