From: Kevin Carhart <kevin@carhart.net>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] regex criteria interpreted as literals
Date: Wed, 13 Jan 2016 18:28:54 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1601131812120.14365@carhart.net> (raw)
In-Reply-To: <87si2190hb.fsf@mushroom.localdomain>
>
> Hi Kevin,
> Nah, this is perfectly fine JavaScript, but Tidy-HTML5 doesn't like it.
> Apparently it converts
> va = /</g;
> to
> va = /<\/g;
> when in fact it should probably just leave it alone. I thought we'd
> gotten through all of this stuff way back in October, but maybe not.
Thanks Chris! Do you think I ought to file this in the requests tracker
for Tidy, also a question for Geoff if you're around?
If you could share the logic with me of how the parser will disambiguate
this, if you know, I'm interested. I can understand why it
would escape </ to <\/ if these two characters are indeed the beginning of
a closing HTML tag. So is the relevant hook for knowing whether to do
so, the fact that we're already inside <script></script>, and you don't
need to escape within that?
(More of a tidy question but not too far afield I dont think..)
thanks
Kevin
next prev parent reply other threads:[~2016-01-14 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 6:01 Kevin Carhart
2016-01-13 6:13 ` [Edbrowse-dev] fixing my semantics a little Kevin Carhart
2016-01-13 11:34 ` [Edbrowse-dev] regex criteria interpreted as literals Chris Brannon
2016-01-14 2:28 ` Kevin Carhart [this message]
2016-01-15 21:38 ` [Edbrowse-dev] Tidy and various tags was " Chris Brannon
2016-01-15 21:46 ` [Edbrowse-dev] Tidy and various tags was regex criteria Karl Dahlke
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=alpine.LRH.2.03.1601131812120.14365@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@the-brannons.com \
/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).