Last modified: 2006-12-12 12:40:36 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 4807 - "Hide my edits" on watchlist resets time to default
"Hide my edits" on watchlist resets time to default
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-01-31 11:44 UTC by Chris M
Modified: 2006-12-12 12:40 UTC (History)
0 users

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


Description Chris M 2006-01-31 11:44:22 UTC
Clicking on "Hide my edits" on a watchlist resets the duration to the default, i.e.

1. Click a time other than the default on the watchlist (e.g. 7 days) and (e.g.
7 days) of edits are shown
2. Click "Hide my edits" and only the edits from the default period (e.g. 12
hours) are shown, but your edits are hidden.
3. Click on the different time again and you can see the edits from (e.g. 7
days) with yours hidden.

Changing the order i.e. step 2 then step 1 and this works as expected.

I have reproduced this several times on en.wp, commons and meta on two different
computers (1 Windows XP, 1 Linux). It does not seem to matter whether the
default time is 12 hours or 3 days.
Comment 1 Antoine "hashar" Musso (WMF) 2006-12-11 20:00:26 UTC
Cant reproduce it with 1.9alpha r18226
The bug probably got fixed somehow :)

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