| Merijn2 | |
| Thu, Oct 29, 10:42 PM |
| F111329511: Screenshot From 2026-10-30 05-37-36.png | |
| Fri, Oct 30, 4:40 AM |
Steps to replicate the issue (include links if applicable):
What happens?: nothing
What should have happened instead?: a list of languages should appear
Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):
Other information (browser name/version, screenshots, etc.): This happened both in opera and edge, on a windows 11 computer
go to any wikipedia page that has version in multiple languages
Hi, please always include links to avoid ambiguity and to allow someone else to reproduce. Thanks.
Same issue. Happens across all en. pages. Other languages perform as expected. Happens on all tested browsers (Chrome, Firefox, Safari). Temporarily fixed with document.querySelector('#p-lang-btn .vector-dropdown-content').style.display = 'block'; until reload
Cannot reproduce in Firefox 158 on English Wikipedia when logged out, Languages dropdown shows (if that's meant here?) and opens:
It seems this issue is on some computers. I seen another report (no other details, example article works for me).
Maybe something with cache.
Informations about browsers (especially if other than from this report) and from browser console would be helpful.
For me, this issue started happening yesterday (Oct 29) and stopped happening just now, after I created a Wikimedia account to create this comment. The issue was affecting some articles but not others.
Example of affected article (language tab didn't drop down when clicked)
https://en.wikipedia.org/wiki/MSX
Example of unaffected article (language tab dropped down normally)
https://en.wikipedia.org/wiki/MSX_(disambiguation)
I tested various pages on Firefox and Chrome on two different devices, and it was always the same articles that were affected and unaffected, so it doesn't appear to be a browser compatibility or browser cache issue.
A user on Finnish Wikipedia reported about occasitionally seeing the same bug on Firefox, Opera and Edge on Windows 10. They couldn't figure out any logic behind when the bug appears and when not.
