From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] amazon and its JS
Date: Sat, 13 Jan 2018 09:11:01 -0500 [thread overview]
Message-ID: <20180013091101.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1801121558330.1675@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
I too have been remiss in my work on edbrowse; there are so many life events clammering for my attention, some of them serious.
> I haven't weighed in on amazon lately, because I can't get it to budge.
This is very frustrating because it seems to work for me,
and I can't imagine what the difference is.
Worse still, Chuck gets a seg fault.
Maybe I could log into his machine and try to track that one down.
I don't deminimize; how does amazon behave if you don't deminimize. Just trying to cut out another variable.
You're right, amazon does so much that if we get it working that bodes well, and probably a lot of other sites will work too.
document.cookie should work. It's been around a while and reasonably well tested.
There should be no trouble replacing window.alert.
Karl Dahlke
next prev parent reply other threads:[~2018-01-13 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 0:12 Kevin Carhart
2018-01-13 14:11 ` Karl Dahlke [this message]
2018-01-13 15:55 ` Chuck Hallenbeck
2018-01-13 16:27 ` Dominique Martinet
2018-01-13 17:12 ` Dominique Martinet
2018-01-13 22:06 ` 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=20180013091101.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).