From: Chris Brannon <chris@the-brannons.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] regex criteria interpreted as literals
Date: Wed, 13 Jan 2016 03:34:40 -0800 [thread overview]
Message-ID: <87si2190hb.fsf@mushroom.localdomain> (raw)
In-Reply-To: <alpine.LRH.2.03.1601122147530.29576@carhart.net> (Kevin Carhart's message of "Tue, 12 Jan 2016 22:01:55 -0800 (PST)")
Kevin Carhart <kevin@carhart.net> writes:
> ua=/</g;va=/>/g;
*SNIP*
> this one is harder to deal with because it isn't delimited by quotes?
> It gets ambiguous to know what /</ means.
> Or should this work?
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.
-- Chris
next prev parent reply other threads:[~2016-01-13 11:33 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 ` Chris Brannon [this message]
2016-01-14 2:28 ` [Edbrowse-dev] regex criteria interpreted as literals Kevin Carhart
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=87si2190hb.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=kevin@carhart.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).