From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <arthompson1990@gmail.com>
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com
 [IPv6:2a00:1450:400c:c05::22b])
 by hurricane.the-brannons.com (Postfix) with ESMTPS id D60F67891D
 for <edbrowse-dev@lists.the-brannons.com>;
 Fri, 11 Sep 2015 00:37:07 -0700 (PDT)
Received: by wicge5 with SMTP id ge5so51985751wic.0
 for <edbrowse-dev@lists.the-brannons.com>;
 Fri, 11 Sep 2015 00:39:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=date:from:to:cc:subject:message-id:references:mime-version
 :content-type:content-disposition:in-reply-to:user-agent;
 bh=75FPOPwG1SDUrML/kzEOEAiH2A8Bw/4p1PAL8PDel2Y=;
 b=nQtL6as4BNwMShURy+scoJtxKDPXTUUYlV3ylF0MqnucRyoRvOFtwUqjMl7G5AGE2m
 LkDPIZMXFHDy4Ch15s604thSuFcacwgDII4Y7KSFLIuADWn/F3ZKWLqB8NKxEp+kKUAb
 1eDf58YD5xXUQ+LAroZUT0+fHo/kHU0mUN+q1gFjAsa1uwV9PEY+hjphiol7ElYB0Ssz
 Hqsvj+CbiswrZrpjAarzSznm0uLYCjNLafwKLan0Gfbs5ktGQQgi2JCmn8cwmNy9qyxb
 +RBNt8U/6NmxeoSmHBP9sOhvuwubo+sULwg3EWHXPd5T7jAZJ9VnWh+syRqKjoazrPkR
 tIVQ==
X-Received: by 10.180.74.148 with SMTP id t20mr14579040wiv.31.1441957186305;
 Fri, 11 Sep 2015 00:39:46 -0700 (PDT)
Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk.
 [2001:8b0:1142:9042::2])
 by smtp.gmail.com with ESMTPSA id 12sm342643wjw.15.2015.09.11.00.39.44
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Fri, 11 Sep 2015 00:39:45 -0700 (PDT)
Date: Fri, 11 Sep 2015 08:39:39 +0100
From: Adam Thompson <arthompson1990@gmail.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Karl Dahlke <eklhad@comcast.net>, edbrowse-dev@lists.the-brannons.com
Message-ID: <20150911073939.GA29720@toaster.adamthompson.me.uk>
References: <55F21D99.7070701@pcdesk.net> <20150810211023.eklhad@comcast.net>
 <alpine.LRH.2.03.1509102200340.19704@carhart.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z"
Content-Disposition: inline
In-Reply-To: <alpine.LRH.2.03.1509102200340.19704@carhart.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [Edbrowse-dev] script tags in scripts
X-BeenThere: edbrowse-dev@lists.the-brannons.com
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Edbrowse Development List <edbrowse-dev.lists.the-brannons.com>
List-Unsubscribe: <http://lists.the-brannons.com/mailman/options/edbrowse-dev>, 
 <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=unsubscribe>
List-Archive: <http://lists.the-brannons.com/mailman/private/edbrowse-dev/>
List-Post: <mailto:edbrowse-dev@lists.the-brannons.com>
List-Help: <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=help>
List-Subscribe: <http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev>, 
 <mailto:edbrowse-dev-request@lists.the-brannons.com?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2015 07:37:08 -0000



--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 10, 2015 at 10:28:03PM -0700, Kevin Carhart wrote:
>=20
> Interesting.. Karl, does your certainty mean that you are saying
> that the distinction between the two tags is fundamentally
> unknowable for a parser?

It's certainly difficult if the parser isn't also capable of parsing the
scripting language within the script tags.

> I guess one good sign is that there appears to be a lot of
> past literature on this issue, on Tidy listservs.  Including
> one from 2006 called "Tidy barfs on split <SCRIPT> tags".
> Unless it's an impossible problem, maybe these past threads
> will contain something we can use.  I will read some of this
> correspondence.

I've also ran the example through the main tidy html5 version and it also s=
pits it out.

> This reminds me of other gnarly situations with literals.
> For instance, when there are regular expression criteria in
> javascript strings that contain just solely a close brace or close
> parenthesis, if I come along and want to make
> assumptions about pairs of braces, the unmatched literal gets me
> out of sync.

Agreed, literals in scripts can cause issues like this.
There's also the issue of json shoved in script tags etc (I've seen web apps
use this for pre-caching server responses).

I'm not sure what we can do about this,
but I'm inclined to think that whatever we do won't catch every case and th=
at
at some stage we have to accept that and move on.
I seem to remember that the accepted "fix"
for this in html is not to split the script in </script> but rather to spli=
t it at the / thus:
document.write("<"); document.write("/script>");
But I may be wrong there.

We should probably report a bug against tidy5 in any case for this.
That's why we're using a parsing library after all.
At least this one's maintained for us so there's a reasonable chance they'll
fix these things once they work out a workable solution.

Cheers,
Adam.

--7AUc2qLy4jB3hD7Z
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJV8oU7AAoJELZ22lNQBzHOLgkH/RfwWcvRbRMgdchW753iOdbh
tB/fT3SdQOdDgPGEz+pFGJ3P652CeziKqceCGsLR8Y9csHynIfE3Z0/Ivy7VbWAg
Ijcr48lFE1BZDxNcVvODNR1BM8IsV/6Sk8H9MheSpWLOdkZ0dXdZMd8UN4sX++4Q
434G+Qg1BUygFlTs524u3FsLenxLNJ/fZFo1DCs0qg7ErCEZYWatQ8QSrC4FVTas
FgpfA7OcN0CreZCGq2enfZmeRMbg0WxAGd2UUqxTxL/Sth7Bq/zXSgTqup9SX7jf
IDHvurTld/g7p9CRyggNHypdQRgkVo3IcuJFfVy6l3ssskSmsWRDXZthf9HKWwg=
=SaJF
-----END PGP SIGNATURE-----

--7AUc2qLy4jB3hD7Z--