Topic on Project:Support desk

Ever since I updated to MW 1.26, when editing pages my monospaced font on the edit page is gone (however not on pages edit via the semantic forms extension ("edit with form"). Do you know how I can restore the monospaced font? Thanks a lot,

Hans

Go to Special:Preferences#mw-prefsection-editing.

Thanks, and sorry I forgot to mention that this setting does not seem to have any effect. Neither does setting the number of columns to e.g. 55. However setting a smaller number of rows, e.g. 5, does work. Puzzling, isn't it?

Maybe you have Universal Language Selector installed? This was happening some time ago because of a bug on that extension

No, Universal Selector is not installed. - The wrong font also appears in the "old" editor window, i.e. when WikiEditor extension is disabled. However the monospaced font correctly appears when editing the page content (free text area) using the Semantic Forms extension.

You can inspect the textarea with developer tools of your browser (right-click → inspect element, or hit F12 and use the inspect this element tool), looking at the CSS rules applied to the textarea, to see what styles are applied and maybe have a hint as of what is changing that appearance. Using "debug=true" in the URL often helps identifying what CSS file is responsible of each style.

I have further digged into this. The obvious difference when inspecting the html is that in my cases (in 3 wikis) the textarea element is assigned class="mw-ui-input", whereas in a fourth fresh test wiki this class assignment is not there.

This seems to be a long known, nasty MW bug:

https://phabricator.wikimedia.org/T92496

https://phabricator.wikimedia.org/T72028

https://phabricator.wikimedia.org/T95831

Possibly the workaround $wgUseMediaWikiUIEverywhere is gone in MW 1.26.3

I am still unable to understand why in my test wiki the effect does not occur. Maybe the different php version and windows instead of debian OS.

Probably have to wait until the core team fixes this. Hopefully they are at least aware of this.

Cheers,

Hans

Try removing extensions one by one and see if you find the culprit.