Page MenuHomePhabricator

Minor edit marker not shown on watchlist when using enhanced recentchanges
Closed, ResolvedPublic

Description

From [[WP:VPT]]: The letter tags for minor edits ("m") and bot edits ("b") in page histories and my watchlist are no longer showing in bold type for me.


Version: 1.18.x
Severity: normal

Details

Reference
bz31408

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:48 PM
bzimport set Reference to bz31408.
bzimport added a subscriber: Unknown Object (MLST).

Fixed in r99089, fix deployed, confirmed working on enwiki.

From http://en.wikipedia.org/w/index.php?diff=454554350

I can see N and b tags on my watchlist, but not m for minor edit. All three tags appear in article history listings. Running Firefox 7.0 on openSUSE. Vector skin with the updates for bold N, b, m tags in common.css. Page reloaded with shift-reload, still happens.

I cannot reproduce. There are bold m's for minor edits on my enwikipedia watchlist.

Created attachment 9249
Watchlist not showing 'm' when relevant

Working for me on en.wiki and it.quote but not Commons (?), see screenshot where some minor edits are not marked as such, e.g. https://commons.wikimedia.org/w/index.php?title=MediaWiki_talk:Gadget-GallerySlideshow.js&curid=11862216&diff=61198807&oldid=61198670

Attached:

WatchlistMinor.png (768×1 px, 275 KB)

A picture says a thousand words.

It appears you're using enhanced rc. I can confirm with enhanced rc enabled, that the minor edit marker is not present.

Caused by a typo in r79085. Fixed with r100510

Created attachment 9297
Enhanced RC + Expand watchlist on Commons (r100918)

For the record, the tricky thing here was that if "Expand watchlist to show all changes, not just the most recent" was enabled (as on it.quote for me) the tag was shown also despite enhanced RC: I checked three wikis and each one had a different configuration. :-p
Congrats for noticing and fixing it. ;-)

Attached:

WatchlistExpanded.png (768×1 px, 253 KB)

  • Bug 33371 has been marked as a duplicate of this bug. ***