Chuck Houpt wrote: What needs to be done to fix this problem? What is the Validator now using JavaScript for? And how can we make this usage of JavaScript /optional/ again? I'm going to guess that the issue isn't the Validator itself, but its web-host/CDN Cloudflare. A few years back, the Validator switched to using Cloudflare to protect it from DDoS attacks and over-zealous checker scripts. When Cloudflare thinks there's "too much" traffic from one source, it will put up a CAPTCHA challenge page. Unfortunately, the challenge page usually requires Javascript as well as other popular-browser features. Thus text-browsers often can't complete the challenge. Even a non-text browser with JavaScript enabled (SeaMonkey 2.53.18.2) is regarded as "unacceptable" by Cloudflare, at least as far as the Validator is concerned. Oh for the idyllic days of Gerald Oskoboiny’s "Kinder, gentler, validator", when validation success was not dependent on the phase of the moon and things "Just Worked" ™ ... -- Philip Taylor This email, its contents and any attachments are intended solely for the addressee and may contain confidential information. In certain circumstances, it may also be subject to legal privilege. Any unauthorised use, disclosure, or copying is not permitted. If you have received this email in error, please notify us and immediately and permanently delete it. Any views or opinions expressed in personal emails are solely those of the author and do not necessarily represent those of Royal Holloway, University of London. It is your responsibility to ensure that this email and any attachments are virus free.
Received on Monday, 12 August 2024 12:56:32 UTC