W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2009

[whatwg] HTML 5 Script Tag

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Fri, 14 Aug 2009 18:16:30 -0400
Message-ID: <7c2a12e20908141516h3c74e1a0k9259ad9ebf286344@mail.gmail.com>
On Fri, Aug 14, 2009 at 11:48 AM, Cready, James<jcready at rtcrm.com> wrote:
> Except of course for the following: <area> <base> <br> <col> <command>
> <embed> <hr> <input> <img> <link> <meta> <param> and <source>
> And these "obsolete elements" still supported by legacy UAs: <basefont>
> <bgsound> and <wbr>

Those are just unclosed, they're not self-closing.  If you use the
"/>" syntax it's not closing the tag, it's just ignored.  If this
proposal were accepted, <script> would become the only tag in
text/html where "<foo />" is treated any differently from "<foo>".

> <article> == <section> == <div>
> <aside> == <details> == <figure>
> <i> == <em>
> <b> == <strong>
> <span> == <mark>
> <caption> == <legend> (if it was allowed inside <table>)

Those are not redundant.  Each of the features you mention serves a
different purpose from the one(s) you equate it to, and is defined to
have different semantics.  The proposal that Ian was responding to is
to create a new <link rel=script href=foo> construct that would be
defined to be *identical* to <script src=foo></script>, or <style
src=foo></style> defined to be *identical* to <link rel=stylesheet

> It already works this way. The browser ignores everything inside the
> <script> tag the moment you put these three letters inside the brackets:
> "src"

It does not work as desired.  Browsers currently parse any content
from the opening <script> up to the next </script> as being inside the
<script> element (and do nothing with it except stick it in the DOM).
The desired behavior is that the browser close the tag immediately and
treat any subsequent content as being outside the <script>.
Received on Friday, 14 August 2009 15:16:30 UTC

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