Last modified: 2012-05-11 14:36:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10572 - "Mark all pages visited" button needs two clicks
"Mark all pages visited" button needs two clicks
Product: MediaWiki
Classification: Unclassified
Watchlist (Other open bugs)
PC Windows XP
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-07-13 19:58 UTC by Rémi Kaupp
Modified: 2012-05-11 14:36 UTC (History)
1 user (show)

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


Description Rémi Kaupp 2007-07-13 19:58:51 UTC
On the watchlist, when the button "Mark all pages visited" is available (for instance on Wikimedia Commons), two clicks are usually required on this button to actually the pages visited, instead of one as expected. More precisely, I need to either :
* click on the button and reload the page, or
* click twice on the button,
in order to get rid of the bold, marking pages as "not visited".

The problem occurs with both Firefox and Internet Explorer 7.
Comment 1 Brion Vibber 2007-07-17 19:08:31 UTC
Probably due to use of slave server; the change is made on master and the list is pulled from slave during the same request. With the slave connection already open, it's going to give data from before the change.

A simple change that might help would be to run an HTTP redirect to force a clean reload instead of showing back the list in the same request handler. That might still show you old data if the slave is lagged a bit, but it would probably usually work correctly. Would have the added bonus that hitting 'reload' won't prompt about POST data, which everyone hates.
Comment 2 Brion Vibber 2007-07-17 19:17:06 UTC
Done in r24210

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