Workaround is to just hit enter, you'll be prompted a second time with a new image. :)

*** Bug 15950 has been marked as a duplicate of this bug. ***

marcoscanrib wrote:

The workaround proposed does not resolve the problem, for at least one strong reason: very few people know it ! Besides, although I haven't tested it yet, it seems to me that it will be much slower than the feature we are requesting.

I requested the same and I was informed of this prior request and that my request was deleted. But I believe my reasoning may help to have it accepted, so I copy it below:

"When we edit Wikipedia pages, frequently it is showed a blured code requesting
us to tipe it before our edition may be saved. Nevertheless, many times this
code is unreadable and we type it uncorrectly. Some time goes until another
page is showed reporting the error and requesting a new code to us.

I have seen a good solution to this problem in a site I visited: Beside the
blured code we need to type, it is showed a button that offer the option to
change the blured code, exactly because sometimes it is unreadable. If we click
the button, the code is changed almost instantaneously, saving us a good time
and pleasing us.

Please, insert this button in wikipedia ! You will facilitate and speed our
work in improving it. Thanks."

marcoscanrib wrote:

(In reply to comment #1)

Workaround is to just hit enter, you'll be prompted a second time with a new
image. :)

The workaround proposed does not resolve the problem, for at least one strong
reason: very few people know it ! Besides, although I haven't tested it yet, it
seems to me that it will be much slower than the requested feature.

It's a best practice used on many Websites to request a new image.

The user has often already entered his account details (username, password, e-mail) before trying the CAPTCHA. So he doesn't want to reload the page and loses the information he typed. Plus, most users doesn't know about it, it's not written anywhere, so most willl never try it. They'll be blocked at the CAPTCHA stage.

This is a goob bug to send to the usability and user experience team, I'm adding Trevor Parscal to the CC list.

folengo wrote:

I agree that we need more than the proposed workaround : see also my comment at
http://lists.wikimedia.org/pipermail/wikitech-l/2011-February/051612.html

I predict that if we add this, the account request queue for en.wiki will drop by half.

All that's needed to implement this is a button that reloads the page and passes the fields that are already filled in as query string params.

Bumping priority as a willful instigator :) Maybe I can find time to fix this myself at some point.

With client-side validation currently live on enwiki refreshing the captcha without reloading the full page would definitely be more user-friendly (you won't need to fill out two passwords after each reload).

Please use AJAX if possible (bug 14123).

kurarei wrote:

The changeset for this bug is on https://gerrit.wikimedia.org/r/#/c/44376/
Please code review it.
Thanks!

• Bug 46994 has been marked as a duplicate of this bug. ***

swalling wrote:

https://gerrit.wikimedia.org/r/#/c/44376/ Merged :)