Thu, Jul 18
Selecting the above-mentioned w.wiki/32$ and right-clicking it also doesn’t work in Firefox (it doesn’t detect it as a valid URL and doesn’t give the option “Go To URL” in its context menu).
Wed, Jul 17
Feb 7 2019
Jun 29 2018
Is this deployed already? If so, unfortunately this has not helped with T172392 -- PDFs are still useless at chrwiki.
Jun 4 2018
May 3 2018
I don’t think anybody will object to dropping the gradient, tho (is not a part of the Wikimedia visual language).
Apr 2 2018
Mar 31 2018
I didn’t find the circled question mark distracting at all. It is in fact more distracting now, as this bug report demonstrates. Circled question marks are the norm—they are familiar and predictable (compare e.g. the help buttons in macOS applications, or the little help disks in Windows 7’s Control Panel), and familiarity means no distraction. It was a completely misguided change.
Dec 22 2017
Looking forward to see this fixed; I’ve just uploaded new versions of the Cherokee Wikipedia v2 logos to Commons.
Dec 17 2017
I’d favor justification only if it’s combined with hyphenation; otherwise, the spacing between words becomes ugly and inconsistent.
Nov 26 2017
Nov 22 2017
The referred bug is already fixed in Firefox 58.
Oct 15 2017
Oct 14 2017
Aug 20 2017
Besides the colors, I just wish that we had never added those absolutely hideous-looking, space-wasting, rounded boxes around each single line of text in the diffs. Can we take this opportunity to do away with them?
Aug 3 2017
Jun 13 2017
Jun 5 2017
Oh, if this is the “wrong place”, then fix your tooling. Translatewiki.net sends you here.
Jun 3 2017
Feb 24 2017
Feb 18 2017
Feb 13 2017
Will you consider mobile usage? For example, WhatsApp uses a colored caret. With this, I don’t believe that users will be freaked out by a colored caret.
Feb 7 2017
I’ve marked the extension as archived at https://www.mediawiki.org/w/index.php?title=Extension:Persona&diff=prev&oldid=2360691.
Feb 2 2017
Jan 30 2017
You don’t really need a screenshot, and the OS I use doesn’t really matter; it’s common sense to use text weights/faces for body text and display/light weights for display settings. Unfortunately, using thin, small text has become yet another moronic trend in web design. Sorry for being blunt. Anyway, here are some screenshots of a couple of sites I’ve visited within this hour that have this issue…
Designers shouldn’t punish non-Retina users…
Jan 29 2017
Agreed that it’s too thin. I’m afraid too many designers are wrongly using lightweight faces for body text due to the “fattening” effect of their macOS renderers…
Jan 18 2017
@Volker_E: Mere aesthetic value? That was why I suggested this, of course. I was thinking that the caret could be made to match the color of the focus frame drawn when you click a text field, e.g., when you log into a wiki.
Jan 15 2017
Dec 15 2016
Dec 13 2016
Feb 26 2016
The bug is actually in Skia. Chrome has worked around the bug in version 50.
Dec 12 2015
The problem is more complicated nowadays, since a new Libertine variety has emerged, and which changes the face’s name again (dropping the “Linux” portion due to trademark issues): Linux Libertine O becomes Libertine Serif. I expect this fork to be the replacement of the well-known Linux Libertine O for many users, because the original fonts have long-standing issues and their developer, Philipp Poll, is MIA (thus, this fork).
What about switching the down-arrow icon for an actual pin, instead of relying on an obscure and unclear animation to convey the “pin” behavior? Before finding this bug report (sorry, “task”), I also thought the animation was a bug.
Sep 13 2015
Sep 7 2015
Aug 14 2015
Aug 11 2015
@kaldari: No, I don't think Windows 10 implements anything like automatic font substitution. Georgia Pro is not even installed by default (in order to save space), but you can easily get that (along other updated families) by going to Settings and selecting the "Pan-European Supplemental Fonts" package.
(This comment is more for Gerrit patchset 220610 I guess, but I don't have an account there.)
Apr 3 2015
Thanks for working on this feature! I have a question: