edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Edbrowse Development <edbrowse-dev@lists.the-brannons.com>
Cc: lawrence baggett <baggett@Colorado.EDU>
Subject: [Edbrowse-dev] Continuing Amazon issue
Date: Sun, 7 Jan 2018 15:56:43 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1801071555210.693@debian.pulsar.com> (raw)

Hi everyone,

My Amazon sign-in problem is shared by Larry Baggett, so I'm
copying him on this.  I am including the final dozen or so lines
following submitting my sign-in request with db3 selected.
A script of the failed sign-in effort shows more, it is at:
www.panix.com/~chuxroom/signing-in.txt


Here are the last dozen or so debugging lines:

content application/x-javascript
mod date Mon, 16 Oct 2017 16:18:16 GMT
http code 200
from cache
execute fwcim._CB513135890_.js at 1
execution complete
execute signin at 571
execution complete
execute signin at 592
execution complete
execute onload
execution complete
444
TypeError: undefined not callable (property 'querySelectorAll' of [object Object])
execution complete
TypeError: undefined not callable (property 'debug' of [object Object])
execution complete



Befuddlement also complete! Anybody have any idea? Karl says his Amazon 
sign-in works, but Larry's doesn't, and mine doesn't.


Chuck


-- 
Here In Northeast Ohio also, The Moon is Waning Gibbous (61% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Ashley's iPhone.

             reply	other threads:[~2018-01-07 20:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 20:56 Chuck Hallenbeck [this message]
2018-01-08  1:18 ` Kevin Carhart
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.DEB.2.21.1801071555210.693@debian.pulsar.com \
    --to=chuckhallenbeck@gmail.com \
    --cc=baggett@Colorado.EDU \
    --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).