Last modified: 2010-05-15 15:51:57 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 9973 - "Changed Size" still shows on enhanced recent changes for "collapsed" items
"Changed Size" still shows on enhanced recent changes for "collapsed" items
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-05-20 01:56 UTC by Brad Will (
Modified: 2010-05-15 15:51 UTC (History)
1 user (show)

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


Description Brad Will ( 2007-05-20 01:56:45 UTC
On the recent changes page, if you have $wgRCShowChangedSize set to false, and you have enhanced recent changes enabled in your prefs, you will still see the byte-size change for items that are "collapsed" or "grouped".  

For example, this is what i see for the "collapsed" record on the recent changes:
21:01 Television Appearances‎ (2 changes) . . (+70) . . (Page history)

And, when i expand it, to show the details, this is what i see:
 21:01 (cur; last) . . userid (Talk | contribs | block) (Summary)
 20:39 (cur; last) . . userid (Talk | contribs | block) (Summary)

Since i have the flag set to false, I shouldn't see the byte-changes on any records in recent changes, i think.
Comment 1 Antoine "hashar" Musso (WMF) 2007-05-20 12:01:19 UTC
Fixed in r22280, backported in 1.10.x with r22281.

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