From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (mailfrom) identity=mailfrom; client-ip=8.23.224.61; helo=out.smtp-auth.no-ip.com; envelope-from=kevin@carhart.net; receiver= Received: from out.smtp-auth.no-ip.com (smtp-auth.no-ip.com [8.23.224.61]) by hurricane.the-brannons.com (Postfix) with ESMTPS id DFFF1779FB for ; Fri, 12 Jan 2018 16:08:49 -0800 (PST) X-No-IP: carhart.net@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from carhart.net (unknown [99.52.200.227]) (Authenticated sender: carhart.net@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id BE232440 for ; Fri, 12 Jan 2018 16:12:09 -0800 (PST) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id w0D0C8ld018087 for ; Fri, 12 Jan 2018 16:12:09 -0800 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id w0D0C86D018079 for ; Fri, 12 Jan 2018 16:12:08 -0800 Date: Fri, 12 Jan 2018 16:12:08 -0800 (PST) From: Kevin Carhart To: edbrowse-dev@lists.the-brannons.com Message-ID: User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: [Edbrowse-dev] amazon and its JS X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.24 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 00:08:50 -0000 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