From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] amazon and its JS
Date: Fri, 12 Jan 2018 16:12:08 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1801121558330.1675@carhart.net> (raw)
I haven't weighed in on amazon lately, because I can't get it to budge. I
consistently get kicked back to the login screen.
For lack of any progress on the HTTP sessions, I have gone back to
javascript and am trying to tackle those two JS runtimes.
Also (and related) the events code is in an unfinished state - I'm sorry
for starting this and not following through yet, and thank you Karl for
what you implemented on events recently.
In a while, if not right away, the events code is going to be relevant to
amazon.com. Especially this certain phrasing where one central
listener/dispatcher sits on document on document.body, and events bubble
up from various elements and kick it off. I think that is a common
phrasing. Amazon uses a lot of everything. I noticed that they use
document.cookie.
Here is a specific question. What would happen if page code wants to
overload window.alert? This happens in amazon document.scripts[4].data:
amazon4.js:(function(a){var
b=a.alert;window.alert=function(){a.ueLogError&&a.ueLogError({message:"[CSM]
Alert invocation detected with argument:
"+arguments[0],logLevel:"WARN"});Function.prototype.apply.apply(b,[a,arguments||[]])}})(window);
thanks
Kevin
next reply other threads:[~2018-01-13 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 0:12 Kevin Carhart [this message]
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
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=alpine.LRH.2.03.1801121558330.1675@carhart.net \
--to=kevin@carhart.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).