Re: [edbrowse-dev] home runs (fwd)

[Kevin Carhart <kevin@carhart.net>]

> 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:
<!-- no:cookie fast load the css.           -->

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:
<!-- yes:cookie regular load the cached css -->

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