From: Kevin Carhart <kevin@carhart.net>
To: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
Cc: Edbrowse Development <edbrowse-dev@lists.the-brannons.com>,
lawrence baggett <baggett@Colorado.EDU>
Subject: Re: [Edbrowse-dev] Continuing Amazon issue
Date: Sun, 7 Jan 2018 17:18:36 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1801071708090.15245@carhart.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1801071555210.693@debian.pulsar.com>
Hi Chuck, Larry & list,
I hope we can do something on this, but it's more difficult than usual.
Dominique said:
> I'm not sure I'll be of much help but I'll try to look at it, even if
> the code is obfuscated it should still run in duktape...
I think the current situation is a runtime error or
something unhandled from within the obfuscated file. That's my reason for
thinking that we have to dig in. It's true that we toss endless amounts
of js files from pages into duktape, which work beautifully, and we don't
want or need to care about that JS code.
> TypeError: undefined not callable (property 'querySelectorAll' of [object
> Object])
> execution complete
> TypeError: undefined not callable (property 'debug' of [object Object])
> execution complete
Another tricky thing is that these don't have line numbers attached, so
I'm assuming they are from event handlers, which are no longer in the form
of readable JS. We've mentioned this to Sami as a feature request for
duktape.
I have been working on this over the weekend. I hope we can get through
it and support amazon. Do we know any gangs of CS undergrads with itchy
fingers for an interesting problem?
I'm erring on the side of pessimism given the conflicting reports and
assuming that Karl was able to do something else but not actually get over
the moat yet. Does that seem right, KD?
K
next prev parent reply other threads:[~2018-01-08 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 20:56 Chuck Hallenbeck
2018-01-08 1:18 ` Kevin Carhart [this message]
2018-01-08 2:07 ` Karl Dahlke
2018-01-08 4:16 ` Kevin Carhart
2018-01-08 7:55 ` Karl Dahlke
2018-01-08 7:57 ` Karl Dahlke
2018-01-08 12:07 ` Chuck Hallenbeck
2018-01-08 15:12 ` Karl Dahlke
2018-01-08 15:33 ` Chuck Hallenbeck
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.1801071708090.15245@carhart.net \
--to=kevin@carhart.net \
--cc=baggett@Colorado.EDU \
--cc=chuckhallenbeck@gmail.com \
--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).