From mboxrd@z Thu Jan 1 00:00:00 1970 Received-SPF: None (mailfrom) identity=mailfrom; client-ip=8.23.224.60; 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.60]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 35EF377D97 for ; Mon, 21 May 2018 02:50:06 -0700 (PDT) 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 8E1CE1B1 for ; Mon, 21 May 2018 02:50:07 -0700 (PDT) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id w4L9o4dK007046 for ; Mon, 21 May 2018 02:50:05 -0700 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id w4L9o4f3007040 for ; Mon, 21 May 2018 02:50:04 -0700 Date: Mon, 21 May 2018 02:50:03 -0700 (PDT) From: Kevin Carhart To: edbrowse-dev@lists.the-brannons.com Subject: Re: [edbrowse-dev] home runs (fwd) In-Reply-To: <20180420222456.eklhad@comcast.net> Message-ID: References: <20180420222456.eklhad@comcast.net> User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > Well it's not our highest priority, since I can type hover and bring everything back in, > or better still, run without js, which isn't needed here, > but it just nags at me a bit. Me too, I was hoping to get it. Ok, I do have one more idea that I was pursuing for a little while today! When edbrowse loads the baseball reference, it says in the source, near the top: So then the css is inline and when your CSS code runs in startwindow and gathers the "link" and "style" sources, I believe it picks up the CSS from inline CSS and not also from the file: https://d2p3bygnnzw9w3.cloudfront.net/req/201805182/css/br/sr-min.css Now contrast this with firefox. When I go to the baseball reference in firefox, it says this: There is no inline CSS block. It loads sr-min.css. Now it appears that these two chunks of CSS are different. The inline block has around 24000 characters and it actually ends on : .f-i,#footer,#content,#inner_nav,#srcom{display:none} While the file sr-min.css has 138000 characters and actually contains this: .f-i,#footer,#content,#inner_nav,#srcom{display:none}#footer,#content,#inner_nav,#srcom{display:block} Is it possible that the CSS to set display:block is not reached because of the difference between the inline CSS and the link? Sorry if you've covered this and are aware of this already. I wonder what cookie it's referring to. When I run with db3, it shows that there are plenty of cookies being processed. Kevin