From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] frameElement, infinite loop
Date: Thu, 15 Feb 2018 06:13:29 -0500 [thread overview]
Message-ID: <20180115061329.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
Well that was a few hours of painful stepping through horribly cryptic javascript.
As you recall, www.stackoverflow.com referenced
https://js-sec.indexww.com/ht/p/185901-159836282584097.js
which in turn ran forever, and even ran forever on its own, outside the context of stackoverflow.com.
That's good I guess, it means I only had one file to slog through.
The problem was frameElement, which we never implemented. I didn't even know about it. (This is where the acid tests might help.)
Only took 17 lines, and there it is, and the loop goes away.
That's the thing though, js assumes our browser is perfect, and if it's not, there's no guarantee that js won't go off into an infinite loop.
It usually doesn't, but it could.
Karl Dahlke
next reply other threads:[~2018-02-15 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 11:13 Karl Dahlke [this message]
2018-02-15 18:33 ` Adam Thompson
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=20180115061329.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.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).