UX Suggestion: rm windows alerts

[kuanb]

I would either generate a new modal or have tooltips on the content itself:

Concerns:

• Can be disorienting
• Some browsers may block, in which case page fails silently

Suggestions:

• Use else if statement so that only one windows alert can ever be generated at submission
• Create logic for cancelling without alerts being produced
• For <input>, rely on standard require attributions to force users to input data, with tooltips that pop up so that they can see that (as opposed to validation on submit only that creates those windows alerts)

[radumas]

Thanks for raising this issue! It also came up last night at CfB while someone else was demoing it publicly. Responding to your suggestions out of order

2 Create logic for cancelling without alerts being produced

The commit above deals with this.

3 For <input>, rely on standard require attributions to force users to input data, with tooltips that pop up so that they can see that (as opposed to validation on submit only that creates those windows alerts)

This is already being done. So when the input is invalid the input box gets an angry red border. I just couldn't figure out how to make the tooltips appear by themselves vs. on-hover. Suggestions?

1 Use else if statement so that only one windows alert can ever be generated at submission

I could move the loop to the checker to create one long string of the submission errors which goes into the alert, rather than looping through errors and creating an alert for each.

So I guess 3 would be preferable, and if the tooltips can appear by themselves I should remove the alert. Else fall back to suggestion 1?