edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] amazon and its JS
Date: Sat, 13 Jan 2018 18:12:08 +0100	[thread overview]
Message-ID: <20180113171208.GA20682@nautica> (raw)
In-Reply-To: <20180113162715.GA16048@nautica>

Dominique Martinet wrote on Sat, Jan 13, 2018:
> I have only walked through the very first of these :
> querySelectorAll seems to be invoked from document
>  (e.g. document.querySelectorAll()) modulo tons of obfuscation.
> I thought this would be easy to fix by just adding a line in
> startwindows.js like this :
> document.querySelectorAll = querySelectorAll
> But that doesn't seem to work because querySelectorAll is defined in
> third.js, not sure how to proceed here.

Karl told me where to put that line in third.js, I now have two new
exceptions instead:

TypeError: undefined not callable (property 'getBoundingClientRect' of
[object Object]) (line 1)
(oddly enough not from duk debugger, only edbrowse sees this one?)

and

caught throw: TypeError: undefined not callable (property 'getExtension'
of [object Object]) (line 18)
(from a timer)

Looking this up getExtension seems to be a webGL thing so probably not
for us... getBoundingClientRect is also something graphical to get the
square coordinates of something, not sure how that'd block us either,
but anything goes.


With querySelectorAll hitting submit after entering my password takes
much longer than it previously did before sending the post request, but
I cannot see any difference with it (the openid.return_to token is different
but it might be everytime):

before:
appActionToken=duOgjKNIs7R4LCPldTzPEC8NUbwj3D&appAction=SIGNIN&openid.pape.max_auth_age=ape%3AMA%3D%3D&openid.identity=ape%3AaHR0cDovL3NwZWNzLm9wZW5pZC5uZXQvYXV0aC8yLjAvaWRlbnRpZmllcl9zZWxlY3Q%3D&pageId=ape%3AdXNmbGV4&ignoreAuthState=ape%3AMQ%3D%3D&openid.return_to=ape%3AaHR0cHM6Ly93d3cuYW1hem9uLmNvbT9fZW5jb2Rpbmc9VVRGOCZyZWZfPW5hdl95YV9zaWduaW4%3D&prevRID=ape%3AUzVFMDRRV0NSVzdCVjg5MFRLUFE%3D&openid.assoc_handle=ape%3AdXNmbGV4&openid.mode=ape%3AY2hlY2tpZF9zZXR1cA%3D%3D&openid.ns.pape=ape%3AaHR0cDovL3NwZWNzLm9wZW5pZC5uZXQvZXh0ZW5zaW9ucy9wYXBlLzEuMA%3D%3D&prepopulatedLoginId=&failedSignInCount=ape%3AMA%3D%3D&openid.claimed_id=ape%3AaHR0cDovL3NwZWNzLm9wZW5pZC5uZXQvYXV0aC8yLjAvaWRlbnRpZmllcl9zZWxlY3Q%3D&openid.ns=ape%3AaHR0cDovL3NwZWNzLm9wZW5pZC5uZXQvYXV0aC8yLjA%3D&email=mymail&create=0&password=mypass&signInSubmit=Submit

after:
appActionToken=duOgjKNIs7R4LCPldTzPEC8NUbwj3D&appAction=SIGNIN&openid.pape.max_auth_age=ape%3AMA%3D%3D&openid.identity=ape%3AaHR0cDovL3NwZWNzLm9wZW5pZC5uZXQvYXV0aC8yLjAvaWRlbnRpZmllcl9zZWxlY3Q%3D&pageId=ape%3AdXNmbGV4&ignoreAuthState=ape%3AMQ%3D%3D&openid.return_to=ape%3AaHR0cHM6Ly93d3cuYW1hem9uLmNvbS8%2FX2VuY29kaW5nPVVURjgmcmVmXz1uYXZfeWFfc2lnbmlu&prevRID=ape%3AM1BGOUJNOUFKTjhaUEJWM1JRVDk%3D&openid.assoc_handle=ape%3AdXNmbGV4&openid.mode=ape%3AY2hlY2tpZF9zZXR1cA%3D%3D&openid.ns.pape=ape%3AaHR0cDovL3NwZWNzLm9wZW5pZC5uZXQvZXh0ZW5zaW9ucy9wYXBlLzEuMA%3D%3D&prepopulatedLoginId=&failedSignInCount=ape%3AMA%3D%3D&openid.claimed_id=ape%3AaHR0cDovL3NwZWNzLm9wZW5pZC5uZXQvYXV0aC8yLjAvaWRlbnRpZmllcl9zZWxlY3Q%3D&openid.ns=ape%3AaHR0cDovL3NwZWNzLm9wZW5pZC5uZXQvYXV0aC8yLjA%3D&email=mymail&create=0&password=mypass&signInSubmit=Submit

so I guess this is a dead end...

I have repushed master with querySelectorAll added where Karl suggested,
can't hurt to have for everyone, and moved the debugger code to a new
branch called debugger (still in my tree) to separate the two.

-- 
Dominique

  reply	other threads:[~2018-01-13 17:09 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
2018-01-13 15:55   ` Chuck Hallenbeck
2018-01-13 16:27     ` Dominique Martinet
2018-01-13 17:12       ` Dominique Martinet [this message]
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=20180113171208.GA20682@nautica \
    --to=asmadeus@codewreck.org \
    --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).