@Lazeez Jiddan (Webmaster)
I'm not sure why my browser would be requesting something for the iPad. Until testing with a couple other windows browsers and finding them seeing the same glitched view at the same time - indicating that this was not something my own browser was causing - I'd only connected here using the same windows browser, though version updated a few times over the years. I've never connected here using an Apple device of any kind.
When the glitch happens, I see it if I log in from 3 different browsers, but if I open an incognito or private session where I'm not logged in, I've never seen the glitch there.
The glitch has been around for years, but recently has become more common. It used to be that a simple refresh of the screen was enough to make it go away, and it would stay away for hours if not days. But recently it's common to have consecutive days where that page stays glitched no matter how many times I refresh it.
Recently, I've had the most luck getting the glitch to go away by going into "My Account" and switching to another Theme then switch back again to Classic. But this doesn't always work, and doesn't always keep the glitch at bay for long either.
I used Control-S to save the html page to disk, then I used the html viewer in Altap Salamander to view those saved .htm files, The 3rd party viewer either doesn't support line-boxes, or isn't loading the source where the boxes originate - but I can see the difference between today's glitched page and an older file saved a couple weeks ago without the glitch.
I'm directly sending Lazeez a dropbox link to a .zip containing the glitch and non-glitch version of the html file, so he can confirm what's being received.
Previously, I'd thought that the html for glich and non-glitch were identical except for a few date/time strings, but that's not true. I had been fooled because the control-S save had sent me the non-glitch html even though I was seeing the glitched version on screen. I'm guessing that Ctrl-S doesn't actually save what you're seeing on screen, but instead asks the server for the page again and sends that instead of what you're actually seeing.
Are you sure the browser's requesting the ipad version or is the server just sending the ipad version? I know servers will send different variants of a webpage, depending on which browser is involved, but I thought it was the server asking the browser who they are, and then deciding what to send for that kind of browser. I can't imagine that Internet Explorer, Firefox and Chrome will all 3 decide to identify as iPad at the same time - but never while they're not logged in and never while looking at individual author pages. Then stop saying they're iPad at the same time.