Re: Registration Screen - Warning balloon not sticky
Reply #1 – March 26, 2014, 11:39:40 am
The popup disappears for me no matter what after about 5 seconds. Clicking focus outside the browser does as you mention. Scrolling the screen up and down the balloon is attached to the username for me and stays with it. This is in Chrome latest version. Some uniform validation for all the fields would be nice. Personally I'd rather have the validation happen in both places. Prevent the user from being able to submit with the jquery validation ( I think that is what's used). If the user is able to submit the form without javascript enabled, show them the list of errors above the registration form.
Re: Registration Screen - Warning balloon not sticky
Reply #3 – March 26, 2014, 06:50:43 pm
Emmanuel, thanks for the interesting link. I had no idea that FF 28 was doing this via HTML5. I suppose the good news is that I have found this behaviour only at the registration screen, so far. None of the data input fields in Admin produce an error bubble on bad data, that I have found anyway. I did test it today at SMF using FF 28 and IE 11 and the error message is the standard message below the linktree. No bubble produced at SMF. I have no decision in what happens but my view on the matter is that at present, any error balloon given by the browser would 'break' the visual look of of any theme. So, I would rather see an implementation of the standard error message below the Required Infomation bar, in this case. That warning placement will stay visible to the user until they have entered the proper information ( or some kind of information ) and then submitted the information. With the current balloon warning, it is not sticky to the errored input field (may be browser dependent), disappears and if the user is not attentative they did not catch what the balloon was saying.
Re: Registration Screen - Warning balloon not sticky
Reply #4 – March 26, 2014, 07:01:36 pm
I just looked at this. I agree it seems html5's error checking might be a bit immature. It's email checking isn't even all that rigorous in firefox 27 at least. x@x is a perfectly good email address according to firefox. Maybe Elk should still be handling all the verification itself.