Dirk Fieldhouse wrote on 15/01/2020 2:15 AM:
On 14/01/20 08:20, Daniel wrote:
[email protected] wrote on 13/01/2020 1:38 AM:
<Snip>
Not sure. The presence of "wyciwyg" in the page source when it's
failing to load looks like it could be some interaction between
caching and something JavaScript is doing on those pages.
I'm using SeaMonkey 2.49.5 on Linux Mint.
Don't know if it leads anywhere but ..... "wyciwyg" as in "What You
C(See) Is What You Get"!!
C = Cache
This discussion from 2010
<https://support.mozilla.org/en-US/questions/699151> produced several
plausible suggestions (eg, Safe Mode, clear browser cache, clear DNS
cache, kill googleanalytics, etc, with fire, change DNS servers) but
didn't seem to find a definitive solution.
/df
O.K., but my C for (See) makes sense ..... to me, at least!
--
Daniel
Win7 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0)
Gecko/20100101 SeaMonkey/2.49.5 Build identifier: 20190609032134
Linux User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0)
Gecko/20100101 SeaMonkey/2.49.1 Build identifier: 20171015235623
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
