Last modified: 2013-09-30 23:12:33 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 T56203, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54203 - Core-ify the CleanChanges extension's intent (to filter RecentChanges when it is busy)
Core-ify the CleanChanges extension's intent (to filter RecentChanges when it...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Recent changes (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: design
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-17 02:17 UTC by James Forrester
Modified: 2013-09-30 23:12 UTC (History)
12 users (show)

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


Attachments

Description James Forrester 2013-09-17 02:17:12 UTC
As per Erik's comments in bug 53541 comment 18:

| 1) The extension itself clearly still needs UX love. The filter UI is already
|    cluttered, labels like "Users (Sep: |)" and confusing icon choices (magnify
|    icon to expand links) don't help.
|
| 2) RecentChanges is a core feature. New extensions/features need to tie into
|    it all the time. Maintaining an extension for some subset of wikis that
|    choose it and ensuring its compatibility with all future code strikes me as
|    needless complication of our core UI.
|
| In other words, if these improvements are worthwhile (and I'm not disputing
| they are! Credit to Niklas and the translatewiki.net folks for fixing issues
| in their workflow), I would argue that they should be made in MediaWiki core,
| and consistently applied across all wikis, ideally after some more UX
| attention.

Creating here without specific judgement.

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


Navigation
Links