- From: Brett Zamir <brettz9@yahoo.com>
- Date: Sun, 13 May 2012 22:40:17 +0800
- To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Cc: whatwg <whatwg@whatwg.org>
On 5/13/2012 5:23 PM, Benjamin Hawkes-Lewis wrote: > On Sun, May 13, 2012 at 1:47 AM, Brett Zamir<brettz9@yahoo.com> wrote: >> 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)? > "server-side files to be created" - what do you mean? So, no matter the Server-side JavaScript engine, one could write code like tihs: <p>You loaded this page on <script server> print(new Date()); </server></p> which would become: <p>You loaded this page on Sun May 13 2012 22:33:28 GMT+0800 (China Standard Time)</p> > What would this attribute do? It would simply be reserved for server-side consumption, whether such applications would replace the contents of the tag with HTML or perform some non-transparent actions and just remove the tag. It would not do anything on the client-side (though it wouldn't need to restrict the default behavior either since it really should be consumed by the time it reaches browsers). The purpose is simply to allow server-side applications (such as within templates) to be able to use one HTML syntax portably across other server-side HTML+JavaScript generating environments (and also not be concerned that, as with data-* attributes, that there might end up being some other future use of the attribute by client-side HTML). Brett
Received on Sunday, 13 May 2012 14:40:58 UTC