I'm working to make a script to limit login failures in time.
However, on the phone browser, there could be a white screen with ok (too small to read--it just looks blank) or or white screen with bad password or white screen that said something about username (too small to read but I think it meant the username was typed wrong).
The 'lost on a white screen' problem is a little more frequent for the phone than the PC.
The user may be confused or believe the server is broken/offline.
Feature request:
I'd like a 1 second (maybe 1.5s) redirect on those 3 white screens, such as:
if ok, wait 1s then redirect to ../ (if accidentally at server response screen)
if bad password, wait 1s then redirect to /~login (if password typo)
if bad username, wait 1s then redirect to /~unauth (if can't type own name)
The suggestion is a 'fallback' just to let the users escape from the white screens. I think that problem is raw server-response screens (like white underwear), not developed web pages. But actually redirecting to any page with links is fine--Just really anything other than the mostly blank white screens.
P.S. I did not test with the inbuilt template. This is a basic usability difference between 2.3 vs 2.4: While 2.3 would always reach a web page with clickable links or [section], 2.4 sometimes doesn't. That needs some server-side validation redirect-to-section added.
P.P.S. For me, this is the only impasse between rc versus production release--it is why I can't use 2.4 on my own home server.