Last modified: 2010-09-17 14:18:45 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 23788 - Page byte sizes color coded if larger/smaller
Page byte sizes color coded if larger/smaller
Status: RESOLVED DUPLICATE of bug 24419
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-04 10:30 UTC by FT2
Modified: 2010-09-17 14:18 UTC (History)
2 users (show)

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


Attachments

Description FT2 2010-06-04 10:30:05 UTC
When reviewing a page, especially a talk page, it's useful to be able to visually identify edits that reduced the page size - these are often signs of vandalism, removal of comments, archiving, etc and of interest.

Can byte sizes be color coded red = smaller than previous revision, green=larger?

Also if possible some kind of higher visibility tag, like a color background to the byte field, for larger additions/removals (say > 500 bytes?)
Comment 1 Chad H. 2010-09-17 13:44:52 UTC
Are you talking about on the history page? If so, I think it's a dupe of bug 24419.
Comment 2 FT2 2010-09-17 14:18:45 UTC
Or 24419 is a duplicate of this. Same thing.

*** This bug has been marked as a duplicate of bug 24419 ***

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


Navigation
Links