Page MenuHomePhabricator

Different behavior of mw-diff-movedpara-(left|right) symbol in Timeless
Open, Needs TriagePublic


List of steps to reproduce (step by step, including full links if applicable):

What happens?:
The symbol of mw-diff-movedpara-(left|right) class looks different in timeless.

image.png (120×218 px, 10 KB)
image.png (89×164 px, 5 KB)

What should have happened instead?:
They should have a same view.

Software version (if not a Wikimedia wiki), browser information, screenshots, other information, etc.:

  • 1.39.0-wmf.17 (27d58b4)
  • OS: Microsoft Windows Version 21H1 (OS Build 19043.1645)
  • Browser: Google Chrome Version 102.0.5005.115 (Official Build) (64-bit)

Event Timeline

Stang renamed this task from Different behavior of mw-diff-movedpara-(left|right) symbol to Different behavior of mw-diff-movedpara-(left|right) symbol in Timeless.Mar 14 2022, 7:31 PM
Stang created this task.

I'm not able to reproduce this, regardless of login state (anon or logged in). :-/

Furthermore according to codesearch there aren't too many matches for "mw-diff-movedpara"; the ones relevant to WMF setup are MW core and the MinervaNeue skin. MinervaNeue merely hides the pseudoelement.

Is the bug still present there for you? Are you sure there's no site/user/gadget-specific CSS which could be causing this?

Izno changed the subtype of this task from "Bug Report" to "Task".EditedThu, Jun 23, 2:23 PM
Izno added a subscriber: Izno.

This isn't a bug but instead two different operating systems and/or font stacks selecting a different appearance: both appearances are valid. I recall the Unicode Sol being used liberally on en.wp as a marker for the sun and some OS update changed the appearance to something similar on the left for some people, which got a VPT thread. It was long ago enough that I couldn't tell you whether it was a new font stack or OS.

I don't think there's anything to be done here, but you could sell me on this being a task to reduce the available font sets in an attempt to make it consistent. Either way, not a bug.

Sure that this is not a self/site defined CSS rule (tested in safemode).