Microsoft Edge began missing pictures and scrambling pages again, this time I had disabled all caching. I even did a temporary disable of the Content Delivery Network (CDN) included with my hosting plan to see if that helped. After several hours, Edge and Chrome were still acting up. Firefox and SeaMonkey all never missed a beat! I didn’t check Konqueror in Linux this time, but it never had any issues previously.
You can’t just “turn off” your CDN, if you have one set up. Setting it back up also takes a bit of time. I’m hoping I gave all the caches I couldn’t empty manually time to empty.
This is why I haven’t posted the last few days (besides trying to get a project going). SeaMonkey renders many pages differently, and I thought that it might also balk at displaying images, but it didn’t. Edge and Chrome not only refused to display images until I refreshed the page at least once, but they also royally messed up displaying the pages altogether. I should have gotten a screenshot, but didn’t think about it in time. They really can jumble things around when they want!
The picture on top is how Firefox looks.
Speaking of SeaMonkey, the picture on the right is how it renders the entry page to the blog. It won’t put the spaces between the columns. The picture galleries look and behave very differently, too.
Everything in SeaMonkey works, they simply look different. The picture shows a just-installed SeaMonkey with no add-ons or plugins to make sure nothing was affecting page rendering. Edge was still showing garbage when I took this screenshot of SeaMonkey.
SeaMonkey’s Page Rendering
As an aside, I want to create pages where you can enlarge the pictures in the pages….some day soon, I hope!
Edge renders pages differently from Firefox and Chrome, but not differently enough to justify adding pictures. Mainly, it seems that all the browsers render each page at a slightly different scale. Even Firefox looks different in scale between Windows and Linux. that really may be more of a graphics card difference than the browser or operating system.
So, that’s the latest I guess on the saga of getting things going for real. Once again, things may change appearance or even break with no notice as I figure out what’s happening to Edge and Chrome. To be honest, I’ve always found Firefox to be much more reliable than either Edge or the old Internet Explorer.
It may be an opportunity to play around with a few features as I try to find hope for Edge and Chrome. What appears as scrambled CSS files and the picture loading issues may or may not be related. There are ways of speeding up page rendering by reducing calls to the server by combining different parts of the page when the page is rendered. My first thought was that too many cooks were in the kitchen trying to do the same thing. After disabling everything I could find that speeds up page rendering, I’m not sure now!
Time to get to figuring it out….again…..
