Last modified: 2009-09-08 12:43:27 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 20058 - Add option for editors in preferences to always show diff to latest flagged revision
Add option for editors in preferences to always show diff to latest flagged r...
Product: MediaWiki extensions
Classification: Unclassified
FlaggedRevs (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Aaron Schulz
Depends on:
  Show dependency treegraph
Reported: 2009-08-03 20:51 UTC by P. Birken
Modified: 2009-09-08 12:43 UTC (History)
1 user (show)

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


Description P. Birken 2009-08-03 20:51:38 UTC
It would be nice to have an option for editors in the preferences for the following case:

By default, logged in users always see the latest revision. In the case the latest revision is not flagged, the GUI shows this. If you want to flag that revision, you should first check the diff to the last flagged revision, which requires one more click. So, it would be nice to have an option in the preferences that will cause you to directly see this diff, instead of the draft version. This would save one click, which is nice enough.
Comment 1 Aaron Schulz 2009-08-11 02:37:16 UTC much demand is there for this?
Comment 2 P. Birken 2009-08-19 10:25:18 UTC
Back from holiday: I asked what people though about this and some said that they would use it. So, demand is not overwhelming, but definitely there. 
Comment 3 Aaron Schulz 2009-08-31 06:46:02 UTC
hmm, what are the scenarios where this is considered most useful?
Comment 4 P. Birken 2009-08-31 07:16:07 UTC
This is if you just browse the Wikipedia and stumble on an article with revisions in need of flagging. Then, this saves a click and I believe that this click is the one that makes the difference between someone actually flagging that page or just continue browsing without having done so. 
Comment 5 Aaron Schulz 2009-09-03 02:01:03 UTC
I also worry how this will affect large pages that already take ages to render.
Comment 6 P. Birken 2009-09-06 06:11:30 UTC
Well, I'm not sure. Pages with a lot of formulas can be a pain sometimes. But the page has to be rendered anyhow and I never noticed any problems with diff-rendering?
Comment 7 Aaron Schulz 2009-09-06 07:20:37 UTC
I'm not sure if it's as bad as enwiki then...pages like United State/Japan/India/Barrack Obama all have load time issues. Things can be rendering for 20+ sec. If diffs have to be loaded on top of that there is even more lag and a higher risk of timeouts.
Comment 8 P. Birken 2009-09-07 15:58:42 UTC
The difference could be the number of references, which is significantly smaller on de, compared to en. However, since this is supposed to just be an option in the preferences and I don't expect even the majority of the editors to chose this option, I doubt that this might become a serious issue. 
Comment 9 Aaron Schulz 2009-09-08 03:46:06 UTC
Wait, "...instead of the draft version."? So the page would just be the diff and review form?
Comment 10 Aaron Schulz 2009-09-08 04:30:52 UTC
Done in r56014. Diff shows above page content.
Comment 11 P. Birken 2009-09-08 07:09:06 UTC
Ohoh, my fault! I didn't mean "instead", but "in addition". Sorry about that, so the discussion we were having was exactly the right one. 
Comment 12 Aaron Schulz 2009-09-08 12:43:27 UTC
Re-closing (unless there is something else). The diff is above the content, but does not replace it as per #10.

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