From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] tidy script bug workaround
Date: Mon, 14 Sep 2015 18:05:13 +0100 [thread overview]
Message-ID: <20150914170513.GH29720@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150813130545.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Sun, Sep 13, 2015 at 01:05:45PM -0400, Karl Dahlke wrote:
> > Doesn't this miss the also destructive </script problem?
>
> Yes it does, but "</script>" does not seem to appear in the wild.
> In other words, web developers and generators are careful not to crank out
> the string "...</script>..." because </script> anywhere ends the script.
> My parser has made this assumption for ten years, and it's pretty reliable.
>
> They're more than happy to write
> var a = "<script>";
> but not
> var a = "</script>";
> the latter often written as
> var a = "</scr" + "ipt>";
> This too generates a tidy warning, because </s shouldn't appear,
> or </ any letter for that matter,
> but it does not cause trouble and does not derail the script.
> So my early research suggests we're ok here.
Ok that makes sense. In which case I'm unclear as to why tidy5 wouldn't handle
<script inside a script tag. Has anyone posted to their mailing list yet about this?
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-14 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 1:22 Karl Dahlke
2015-09-13 8:17 ` Chris Brannon
2015-09-13 14:46 ` Karl Dahlke
2015-09-13 16:37 ` Adam Thompson
2015-09-13 17:05 ` Karl Dahlke
2015-09-14 17:05 ` Adam Thompson [this message]
2015-09-14 18:37 ` Chris Brannon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150914170513.GH29720@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).