Last modified: 2014-06-05 10:42:13 UTC
There's no need to send the content to the server, a clientwise js check would be much quicker. We could for example reuse the jquery ui to display a simple alert, and if the user dismisses it, but clicks save again, then save it. I'll write up a short js function soon.
(In reply to comment #0) > There's no need to send the content to the server, a clientwise js check would > be much quicker. > We could for example reuse the jquery ui to display a simple alert, and if the > user dismisses it, but clicks save again, then save it. The only advantage to the server-side check is that it works for users with without JavaScript support. A JavaScript check would be great to supplement the current code, though. I'm not sure if there's any standard format for user alerts of this nature currently. You might want to poke Brandon Harris (jorm); he's been doing some style guideline work in this area. It'd be nice to implement these types of alerts in a consistent, sane manner from the beginning. :-)
This is particularly important for the Wikipedias which enable this option by default in a way or another: requiring reload reduces successful edits drastically.
