Page MenuHomePhabricator

wikipedia.org wordmark sprite in wrong position on resolutions <=480px
Closed, ResolvedPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

What happens?:

The Wikipedia wordmark logo does not show, instead you see half of the WMF logo.

What should have happened instead?:

The Wikipedia wordmark logo should show in full above the text "The Free Encyclopedia".

Other information (browser name/version, screenshots, etc.):

Looks like the logo sprite has been changed and the background-position property on .svg-Wikipedia_wordmark just needs adjusting within the max-width: 480px media query.

Spotted on Google Chrome on desktop using responsive mode (both Mac and PC) and replicated on Google Pixel 6 Pro

image.png (616×885 px, 57 KB)

Event Timeline

Someone also recently reported this on reddit. I was able to reproduce this on Android using both Google Chrome and Firefox. As ehuges said, the positioning of the wordmark gets messed up at the 480px breakpoint, so likely a CSS issue. The root domain of the project is pretty user-visible, so hopefully this can be triaged soon.

Seems like this is caused by T323399. @Jdforrester-WMF, looks like you worked on that?

This has already been fixed by https://gerrit.wikimedia.org/r/c/wikimedia/portals/+/953275 which was tagged against that other task -- I think it's just waiting for a deployment window to go out.

Change 954709 had a related patch set uploaded (by Jdrewniak; author: Jdrewniak):

[operations/mediawiki-config@master] Bumping portals to master

https://gerrit.wikimedia.org/r/954709

Change 954709 merged by jenkins-bot:

[operations/mediawiki-config@master] Bumping portals to master

https://gerrit.wikimedia.org/r/954709

Sorry for the delay, just deployed the fix.

I'm still getting the old CSS locally; is it cached?

Looks okay to me right now, so the caching issue may have passed.

image.png (834×858 px, 106 KB)

Looks okay to me right now, so the caching issue may have passed.

image.png (834×858 px, 106 KB)

Still broken for me; might be a esams vs. eqiad caching issue?

Still broken for me too, and I'm in the Netherlands, so I'm assuming I'm connected to esams.

Fixed now, also using esams.