Once again I have put an apology between the <noscript> tags
Sorry friends, I would have made this work without Javascript, but I didn't have time and at this point, seriously, most websites don't work for you, do they?
(That isn't what I wrote, I just said sorry)
Anyone who is seriously using the web with JS turned off in 2024 must be getting captcha-blocked from half of it and blank pages for quite a lot of the other half
Statistically it's probably more worthwhile testing your site on IE11 than for non-JS users at this point
@robstyles @sil Yes, but a lot of these are just that the browser/connection is broken in some way, which... yeah, you should allow for that. But as an error state, at this point in the web's development, not an entire supported alternative path
@tomw @robstyles ah, a slightly different link might be useful, perhaps. Most people whose JavaScript fails aren’t that way because it’s turned off or they’re in Lynx on a green screen terminal in 1992. It’s a temporary failure; their train went into a tunnel, or they’re on hotel WiFi, or something. And sure, you can say “hit refresh”. But if the page does something useful in that situation, then it works for them and they don’t notice. The next load fixes it.
https://www.kryogenix.org/code/browser/why-availability/ has more.
@sil @tomw @robstyles
Did lynx even exist in 1992? 🤭
I'm not using lynx on a green screen terminal, and I'm most probably not most people, but I use w3m often — and surprisingly, a lot of stuff works.
The CHANGES2.3 file goes back to 12-1-92, so Lynx did [just] exist in 1992 :-)
@sil @tomw @robstyles
I don't think that those who use TUI browsers expect widgets to work — but at least the content should be accessible. It would also be nice for the website to support proper pagination when dynamic loading on scrolling isn't accessible — this is great for both cases: when the connection is poor and when there is no JS at all.