Last modified: 2013-04-22 16:14:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T16230, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 14230 - Add a button to request a new fancy captcha (code)
Add a button to request a new fancy captcha (code)
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
ConfirmEdit (CAPTCHA extension) (Other open bugs)
unspecified
All All
: High enhancement with 9 votes (vote)
: ---
Assigned To: lalei
: easy
: 15950 46994 (view as bug list)
Depends on:
Blocks: ajax
  Show dependency treegraph
 
Reported: 2008-05-22 20:39 UTC by Raimond Spekking
Modified: 2013-04-22 16:14 UTC (History)
17 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Raimond Spekking 2008-05-22 20:39:44 UTC
Add a button to request a new fancy captcha when the given words are unreadable.
Comment 1 Brion Vibber 2008-05-22 21:32:30 UTC
Workaround is to just hit enter, you'll be prompted a second time with a new image. :)
Comment 2 P.Copp 2008-10-12 15:49:06 UTC
*** Bug 15950 has been marked as a duplicate of this bug. ***
Comment 3 Marcos Ribeiro 2008-10-15 04:50:56 UTC
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."
Comment 4 Marcos Ribeiro 2008-10-15 04:57:58 UTC
(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.
Comment 5 Rodan BURY 2010-10-23 13:00:47 UTC
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.
Comment 6 folengo 2011-02-05 13:40:01 UTC
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
Comment 7 Ryan Kaldari 2013-01-04 00:15:03 UTC
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.
Comment 8 Dario Taraborelli 2013-01-04 04:07:58 UTC
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).
Comment 9 Helder 2013-01-10 13:28:12 UTC
Please use AJAX if possible (bug 14123).
Comment 10 lalei 2013-01-17 02:26:32 UTC
The changeset for this bug is on https://gerrit.wikimedia.org/r/#/c/44376/
Please code review it.
Thanks!
Comment 11 Andre Klapper 2013-04-15 12:01:00 UTC
*** Bug 46994 has been marked as a duplicate of this bug. ***
Comment 12 Steven Walling 2013-04-18 22:08:22 UTC
https://gerrit.wikimedia.org/r/#/c/44376/ Merged :)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links