From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] function.toString
Date: Tue, 10 Sep 2019 05:16:23 -0400 [thread overview]
Message-ID: <20190810051623.eklhad@comcast.net> (raw)
As per my earlier email about an infinite loop,
it maybe shouldn't be running that code at all, because of an earlier test.
Consider this.
o = {removeCookie:function(){}}; o.removeCookie.toString();
duktape gives us this.
function () { [ecmascript code] }
But the web page expects it to match the regexp
\w+ *\(\) *{\w+ *['|"].+['|"];? *}
Which it does not, and then it goes down a strange path.
Perhaps you have access to other engines like v8 or js24 etc,
or just put it in an alert in javascript and see what other browsers do with it.
Is ducktape doing something nonstandard?
Karl Dahlke
reply other threads:[~2019-09-10 9:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190810051623.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.org \
/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).