Page MenuHomePhabricator

[Vector] recent changes uses different font for rows showing wikibase-item
Closed, DeclinedPublic


I am using vector Skin. My recent changes list is showing two different fonts.

For an wikidata item the font family sans-serif is defined inline:
<li class="mw-line-even mw-changeslist-line-watched watchlist-0-Q121353">
<span class="wb-itemlink">
<span class="wb-itemlink-label" lang="de" dir="ltr" style="font-family: sans-serif;">(1030) Vitja</span>
<span class="wb-itemlink-id">(Q121353)</span>

For other rows in my watchlist html contain this code:

<li class="mw-line-odd mw-changeslist-line-watched watchlist-9-Gadget-autoEdit_js">
<span class="mw-title">
<a class="mw-changeslist-title" title="MediaWiki talk:Gadget-autoEdit.js" href="/wiki/MediaWiki_talk:Gadget-autoEdit.js">MediaWiki talk:Gadget-autoEdit.js</a>

No font is defined inline that is why my browser is using this css entry:

  • common styles independent from JavaScript being enabled or disabled *
  • @since 0.1
  • @file
  • @ingroup Wikibase *
  • @license GNU GPL v2+
  • @author H. Snater */
  • {

/* defining Arial as default font working around problematic font metrics of Helvetica applied
in Firefox and Opera on Mac cutting off high characters like "Å" in some cases */
font-family: Arial, sans-serif;

Arial is not my default sans-serif font. That's why two fonts are mixed up in recent changes. [Quoted html only shows important hierarchy.]

Version: unspecified
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:10 AM
bzimport set Reference to bz42615.
bzimport added a subscriber: Unknown Object (MLST).

Arial is not always available. I guess this workaround will only work on Windows.

As long as both font definitions are equal it doesn't mapper if Arial is installed or not. Only if Arial is installed, but not the default sans-serif font, fonts are mixed on recent changes view.

The particular declaration was removed some months ago. Can you please re-confirm the faulty behaviour or close the bug if it is not valid anymore?

merl: Could you answer comment 3, please?

merl: Could you answer comment 3 if this is still a problem, please?

Unfortunately closing this report as no further information has been provided.

merl: Please feel free to reopen this report if you can provide the information asked for and if this still happens. Thanks!