Demonstrable regression for Lingala, per
<https://bugzilla.wikimedia.org/show_bug.cgi?id=1941#c16>, and
plausibly for some other poorly-supported scripts as well. Also
harmed some other things:
* Can make it hard to work with multiple scripts generally, since
unusual characters may fall back to proportional fonts for some
characters.
* It's much harder to tell apart some kinds of similar-looking
characters like dashes and hyphens.
Plus a lot of people think it's ugly. Browser consistency shouldn't be
a goal here per se -- different browsers/platforms have different
display conventions, and we should respect that where possible unless it
causes demonstrable problems (which this hasn't AFAICT).
* (bug 5506) Links to files on foreign repositories are now shown consistently
as bluelinks e.g. in logs and edit summaries
* (bug 16623) Add missing </p> tag in Special:LockDB
-* (bug 1941) Explicitly tell browsers to use a monospaced font for textareas.
- Safari apparently defaults to a proportional font, which can make editing
- pages with preformatted text difficult
* (bug 15849) Special:Movepage now throws a more specific error when trying to
move a title to an interwiki target
* (bug 16638) 8-bit URL fallback encoding now set on additional languages using
img.tex { vertical-align: middle; }
span.texhtml { font-family: serif; }
-/* (bug 1941) Safari defaults to a proportional font for textareas */
-textarea { font-family: monospace; }
-
/* add a bit of margin space between the preview and the toolbar */
/* this replaces the ugly <p><br /></p> we used to insert into the page source */
#wikiPreview.ontop { margin-bottom: 1em; }