Greg Wooledge <g...@wooledge.org> wrote: > On Sun, Nov 17, 2024 at 09:34:00 +0000, debian-u...@howorth.org.uk > wrote: > > "Russell L. Harris" <russ...@rlharris.org> wrote: > > > On Sat, Nov 16, 2024 at 01:03:34PM -0500, Greg Wooledge wrote: > > > >I've been thinking about this some more, and I'd like to try to > > > >list all the ways the OP might have caused this to fail. > > > > > > > >We start by observing that nobody else has been able to > > > >reproduce the OP's failure. > > > > > > Two or three months ago, a guy in Australia and a guy in England > > > reported the same problem (blank white screen). > > > > I was the 'guy in England', but that's irrelevant because the > > problem there was sites that were discriminating based on the > > user-agent string supplied by the browser. Here it's simply a > > question of whether the browser has javascript enabled. Same > > symptoms, completely different cause. > > Except the OP in this thread claims he has never disabled Javascript > (didn't even know what that *meant*), and in fact does not yet know > what's causing the problem.
And this guy tried to access the site with javascript disabled (my default) and saw a white screen and then enabled javascript and saw a functioning website. Occam's razor suggests javascript as the factor, and I would further suggest that the OP needs to investigate javascript and determine whether or not they have it disabled (by default). Furthermore in this case I didn't change my user agent string, so as stated, it's a totally different cause for sure.
