MediaWiki talk:Common.css

Request

Could the following code be added to the common.css? (look over it first though) It would help make the messagebox templates look normal. -- Cheers, Riley Huntley 19:44, 23 November 2012 (UTC)

/**
** Messagebox templates
** Imported from [[en: MediaWiki:Common.css]] on 2012-11-23
**/
.messagebox {
    border: 1px solid #aaa;
    background-color: #f9f9f9;
    width: 80%;
    margin: 0 auto 1em auto;
    padding: .2em;
}
.messagebox.merge {
    border: 1px solid #c0b8cc;
    background-color: #f0e5ff;
    text-align: center;
}
.messagebox.cleanup {
    border: 1px solid #9f9fff;
    background-color: #efefff;
    text-align: center;
}
.messagebox.standard-talk {
    border: 1px solid #c0c090;
    background-color: #f8eaba;
    margin: 4px auto;
}

-- Cheers, Riley Huntley 19:44, 23 November 2012 (UTC)

Done. Regards, — Moe Epsilon 04:09, 24 November 2012 (UTC)

Armenian language

Please, hide title of Wikidata:Գլխավոր_էջ page. Add the following selector into Common.css:

.page-Wikidata_Գլխավոր_էջ.action-view .firstHeading,

--Hamlet Muradyan ^talk 11:40, 23 February 2013 (UTC)

 Done. --Stryn (talk) 15:46, 23 February 2013 (UTC)

Hlist classes

{{Edit request}}

Please add "hlist" classes for unification style of navigational templates. This code taken from meta:MediaWiki:Common.css:

Click [expand] to view the content

/**
 * Style for horizontal lists (separator following item).
 * @source mediawiki.org/wiki/Snippets/Horizontal_lists
 * @revision 3.1 (2013-01-16)
 * @author [[User:Edokter]]
 * imported by [[User:Billinghurst]] 2013-01-27
 */
.skin-monobook .hlist dl,
.skin-modern .hlist dl,
.skin-vector .hlist dl {
    line-height: 1.5em;
}
.hlist dl,
.hlist ol,
.hlist ul {
    margin: 0;
    padding: 0;
}
/* Display list items inline and make them nowrap */
.hlist dd,
.hlist dt,
.hlist li {
    margin: 0;
    display: inline;
    white-space: nowrap;
}
/* Allow wrapping for list items (in tight spaces) */
.hlist.hwrap dd,
.hlist.hwrap dt,
.hlist.hwrap li {
    white-space: normal;
}
/* Display nested lists inline and allow them to wrap */
.hlist dl dl, .hlist dl ol, .hlist dl ul,
.hlist ol dl, .hlist ol ol, .hlist ol ul,
.hlist ul dl, .hlist ul ol, .hlist ul ul {
    display: inline;
    white-space: normal;
}
/* Generate interpuncts */
.hlist dt:after {
    content: ":";
}
.hlist dd:after,
.hlist li:after {
    content: " ·";
    font-weight: bold;
}
.hlist dd:last-child:after,
.hlist dt:last-child:after,
.hlist li:last-child:after {
    content: none;
}
/* For IE8 */
.hlist dd.hlist-last-child:after,
.hlist dt.hlist-last-child:after,
.hlist li.hlist-last-child:after {
    content: none;
}
/* Add parentheses around nested lists */
.hlist dd dd:first-child:before, .hlist dd dt:first-child:before, .hlist dd li:first-child:before,
.hlist dt dd:first-child:before, .hlist dt dt:first-child:before, .hlist dt li:first-child:before,
.hlist li dd:first-child:before, .hlist li dt:first-child:before, .hlist li li:first-child:before {
    content: "(";
    font-weight: normal;
}
.hlist dd dd:last-child:after, .hlist dd dt:last-child:after, .hlist dd li:last-child:after,
.hlist dt dd:last-child:after, .hlist dt dt:last-child:after, .hlist dt li:last-child:after,
.hlist li dd:last-child:after, .hlist li dt:last-child:after, .hlist li li:last-child:after {
    content: ")";
    font-weight: normal;
}
/* For IE8 */
.hlist dd dd.hlist-last-child:after, .hlist dd dt.hlist-last-child:after, .hlist dd li.hlist-last-child:after,
.hlist dt dd.hlist-last-child:after, .hlist dt dt.hlist-last-child:after, .hlist dt li.hlist-last-child:after,
.hlist li dd.hlist-last-child:after, .hlist li dt.hlist-last-child:after, .hlist li li.hlist-last-child:after {
    content: ")";
    font-weight: normal;
}
/* Put numbers in front of ordered list items */
.hlist.hnum ol {
    counter-reset: list-item;
}
.hlist.hnum ol > li {
    counter-increment: list-item;
}
.hlist.hnum ol > li:before {
    content: counter(list-item) " ";
}
.hlist.hnum dd ol > li:first-child:before,
.hlist.hnum dt ol > li:first-child:before,
.hlist.hnum li ol > li:first-child:before {
    content: "(" counter(list-item) " ";
}
/* end hlist */

Thanks! --Kaganer (talk) 09:55, 1 March 2013 (UTC)

 Done▬ Reza1615 / T 19:46, 1 March 2013 (UTC)

Thanks. Are used. --Kaganer (talk) 09:07, 3 March 2013 (UTC)

Since gerrit:96071 hlist is in core in module mediawiki.hlist. To use the CSS definition from the module it must be loaded by

mw.loader.load( 'mediawiki.hlist' );

Maybe the module can be loaded in MediaWiki:Common.js by the following code:

mw.hook( 'wikipage.content' ).add( function ( $content ) {
	if ( $content.find( '.hlist' ).length ) {
		mw.loader.load( 'mediawiki.hlist' );
	}
} );

--Fomafix (talk) 13:26, 5 December 2013 (UTC)

farsi font

adding this code to make wikidata's font like fa.wikipedia interface

/* Persian specific customization */
html[lang=fa] body, [lang=fa] {font-family: Tahoma, 'DejaVu Sans', sans-serif !important;}

 Support▬ Reza1615 / T 19:44, 1 March 2013 (UTC)

 Support--درفش کاویانی (talk) 23:03, 1 March 2013 (UTC)

 Support --Pouyana (talk) 09:52, 2 March 2013 (UTC)

 Done▬ Reza1615 / T 09:28, 3 March 2013 (UTC)

Kurdish specific customization

Please add following code for ckb language:

/* Kurdish specific customization */
html[lang=ckb] body, [lang=ckb] { font-family: Tahoma, 'DejaVu Sans', sans-serif !important;}

Thank you.--Calak (talk) 19:49, 1 March 2013 (UTC)

 Done▬ Reza1615 / T 09:28, 3 March 2013 (UTC)

---

Hi

could you add Kurdish?:

.page-Wikidata_Destpêk.action-view .firstHeading,

--thanks--George Animal (talk) 11:53, 10 March 2013 (UTC)

 Done. --Stryn (talk) 12:19, 10 March 2013 (UTC)

af

Please remove the heading on Afrikaans main page (Wikidata:Main Page/af) thank you --Bigbossfarin (talk) 14:36, 25 September 2013 (UTC)

 Done, page also moved to Wikidata:Tuisblad, as it is the Afrikaans name for the main page. --Stryn (talk) 15:29, 25 September 2013 (UTC)

fo

Please remove the heading on føroyskt main page (Wikidata:Forsíða/fo) thank you --Bigbossfarin (talk) 15:12, 2 December 2013 (UTC)

 Done. --Stryn (talk) 15:34, 2 December 2013 (UTC)

Esperanto logo

Please change the logo for Esperanto interface to the Esperanto one. (per Yair rand)

:lang(eo) #p-logo a {
	background-image: url(https://upload.wikimedia.org/wikipedia/commons/thumb/b/b9/Wikidata-logo-eo.svg/156px-Wikidata-logo-eo.svg.png) !important;
}

Thanks in advance! --KuboF (talk)

Reasonator icon

Does someone knows how to make an icon for the {{Reasonator}} or {{Q'}} template that is sized in em ? Mediawiki sizes the images in pixels only and I up to now failed with inline css (the parser defends himself :) Is it possible to include a usable clss for that here ? TomT0m (talk) 11:33, 17 February 2014 (UTC)

MediaWiki only supports image sizes in pixels: mw:Help:Images#Size and frame --Fomafix (talk) 12:41, 17 February 2014 (UTC)

I know that. But CSS is not limited to that and can include images as background images, mediawiki images can be css styled, … TomT0m (talk) 12:53, 17 February 2014 (UTC)

It it not allowed to include background images in inline CSS from wikitext because of security risk. In MediaWiki:Common.css it would be possible to include a background image. To include a background image in MediaWiki:Common.css for a single template is not a good idea. --Fomafix (talk) 12:59, 17 February 2014 (UTC)

@Fomafix: I don't see why, this CSS is almost empty and reasonator is an important tool, it's worth it. And the Q template may be the only Q template (except for Q') it is present on a lot of pages. TomT0m (talk) 16:34, 17 February 2014 (UTC)

What CSS definition do you want to add? --Fomafix (talk) 18:50, 17 February 2014 (UTC)

.reasonator-logo {
    background-image:url(//upload.wikimedia.org/wikipedia/commons/b/ba/Wikidata-Reasonator_small_logo.svg);
	display:inline-block;
    height:1em;
    width:1em;
    background-size:1em 1em;
    background-repeat: no-repeat;
}

This code seems to work fine with () for what we wànt to do, but I'm not a CSS expert.

@Fomafix: Just out of interest. When will MediaWiki support image sizes relative to text size? It seems that amount of devices with high-resolution screens is exploding and for all of those devices images will be very small. Especially already very small icons. --Tobias1984 (talk) 14:58, 18 February 2014 (UTC)

Infoboxes

Now that we have arbitrary access to Wikidata's data, we could build infoboxes using the data. Can I import the infobox part of en:MediaWiki:Common.css ? --Zolo (talk) 06:32, 24 August 2014 (UTC)

Where do you want to use it? Currently MediaWiki:Common.css and in MediaWiki:Common.js are already a lot of stupidly imported code which is unused or deprecated and gets loaded on every page. --Fomafix (talk) 09:59, 24 August 2014 (UTC)

I'd like to test infoboxes on item talk pages, both because it would make neater data, and because this would be a good way to test Wikidata in infoboxes before it can be used in other Wikis. --Zolo (talk) 11:14, 24 August 2014 (UTC)

Why the English Wikipedia's in particular? Should we import the CSS from all wikis that have their own infobox CSS? Perhaps we should import none of them, and just build our own generic/simplistic infobox... which might not even need any special additions to Common.css. --Yair rand (talk) 17:08, 24 August 2014 (UTC)

Yes. Or put the infobox style into MediaWiki directly, so every wiki can use it, without importing a special style into the sites common.css. --Fomafix (talk) 17:17, 24 August 2014 (UTC)

If you want to test, then better to use your local style pages. I agree with Yair rand above to build our own infobox. --Stryn (talk) 18:53, 24 August 2014 (UTC)

I thought English infoboxes were likely to be better maintainted (French infoboxes tend to look nicer but the code is really too complicated and full of legacies).

True that we may not really need css. I had a try at duplicating some useful parts of the French css in Module:Infobox/Style. That does not load on every page and that may be enoug (see Template:Infobox Human/Test). --Zolo (talk) 11:01, 25 August 2014 (UTC)

Restore sitelink alignment

{{Edit request}}

Please add the following to restore the alignment of sitelinks:

.wikibase-sitelinkview-siteid-container {
	min-width: 1.4em;
	text-align: center;
}

Petr Matas 15:21, 21 January 2015 (UTC)

@Petr Matas: -  Done George Edward C – Talk – Contributions 16:34, 25 January 2015 (UTC)

Thanks! Petr Matas 08:31, 27 January 2015 (UTC)

{{Edit request}} Please revert this edit in a few days when this change is merged, deployed and live on wikidata.org. Thank you. --Thiemo Mättig (WMDE) 12:01, 4 July 2016 (UTC)

@Thiemo Mättig (WMDE): done. Sjoerd de Bruin (talk) 14:43, 7 July 2016 (UTC)

Treeview broken in rtl

Could someone please add /* @noflip */ above .treeview li li's padding-left: 20px;? Thanks. --Yair rand (talk) 04:02, 27 April 2015 (UTC)

 Done (diff) --Fomafix (talk) 05:30, 27 April 2015 (UTC)

Bug with template:C ?

Hi, if I type {{C|||}} in the middle of this sentence, there is a line break, but if I type

: after a ":" to indent in a discussion, {{C|||}} there is no line break ...

Hi, if I type {{C|||}} in the middle of this sentence, there is a line break, but if I type

after a ":" to indent in a discussion,

⟨ subject ⟩  Wikidata property  ⟨ object or value ⟩

</nowiki> there is no line break ...

Do you think it's a bug in the CSS ? Any workaround ? TomT0m ^(talk) 16:39, 12 July 2015 (UTC)

Esperanto logo of Wikidata

Wikidata in Bengali and Slovak have their own translated logos. There is also an Esperanto version of this logo, but it is currently not used by the main interface.

Could somebody add the following lines to the following page, under the comment /* Language-specific logos */ to this page:

:lang(eo) #p-logo a {
	background-image: url(//upload.wikimedia.org/wikipedia/commons/thumb/b/b9/Wikidata-logo-eo.svg/156px-Wikidata-logo-eo.svg.png) !important;
}

Robin van der Vliet (talk) (contribs) 12:58, 31 August 2016 (UTC)

done --Pasleim (talk) 13:04, 31 August 2016 (UTC)

Arabic logo of Wikidata

{{Edit request}} Hello.Please add

:lang(ar) #p-logo a {
        background-image: url(//https://upload.wikimedia.org/wikipedia/commons/1/1f/Wikidata-logo-ar.png) !important;
}

Thank you --ديفيد عادل وهبة خليل 2 (talk) 09:27, 14 March 2017 (UTC)

 Done Please check. Matěj Suchánek (talk) 08:22, 15 March 2017 (UTC)

The result

@Matěj Suchánek:This only shows --ديفيد عادل وهبة خليل 2 (talk) 08:42, 15 March 2017 (UTC)

Made it smaller, should be better now. Matěj Suchánek (talk) 09:06, 15 March 2017 (UTC)

Yes, the miniaturization resolved the problem. Thank you. --ديفيد عادل وهبة خليل 2 (talk) 09:20, 15 March 2017 (UTC)

css hooks to hide on print

@media print {
/* css hooks to hide on print */
.displayonly {
  display: none;
}
}

Template:SPARQL2 d1g (talk) 16:14, 1 August 2017 (UTC)

Redirect on Main Page

{{Edit request}} Hi, could someone add something like

.page-Wikidata_Main_Page.action-view #contentSub { 
	display: none;
}

to hide the hint for redirect? --Bigbossfarin (talk) 10:39, 7 August 2017 (UTC)

 Done --Pasleim (talk) 14:41, 21 August 2017 (UTC)

Edit request on 9 January 2018

{{Edit request}} Could the following text, from w:en:MediaWiki:Common.css, be added at line 750? This is because I replaced the (semantically incorrect) definition list items in the property proposal template with <h4>, but they shouldn't display in the table of contents since showing them makes the TOC three times longer and no less^{more 06:12, 12 January 2018 (UTC)} helpful (the headers would all be the same).

/* Allow limiting of which header levels are shown in a TOC;
   <div class="toclimit-3">, for instance, will limit to
   showing ==headings== and ===headings=== but no further */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
	display: none;
}

Thanks, Jc86035 (talk) 10:39, 9 January 2018 (UTC)

 Support Code imported from enwiki, may be useful in project pages.--Ssola (talk) 11:05, 9 January 2018 (UTC)

 Done Matěj Suchánek (talk) 08:36, 10 January 2018 (UTC)

Wikidata logo in Lingua Franca Nova

Could somebody add the following lines to the following page, under the comment /* Language-specific logos */:

#p-logo:lang(lfn) a {
	background-image: url(//upload.wikimedia.org/wikipedia/commons/thumb/a/aa/Wikidata-logo-lfn.svg/156px-Wikidata-logo-lfn.svg.png) !important;
}

Robin van der Vliet (talk) (contribs) 18:44, 13 May 2018 (UTC)

 Done Matěj Suchánek (talk) 07:56, 14 May 2018 (UTC)

Edit request

{{Edit request}}

The revision filter on history pages currently looks broken as reported in phab:T234005. Please remove the following styling as it's no longer necessary.

/* Styling for JQuery makeCollapsible, matching that of collapseButton */
.mw-collapsible-toggle {
	font-weight: normal;
	/* @noflip */
	text-align: right;
}

Ammarpad (talk) 12:47, 27 September 2019 (UTC)

Added {{Edit request}} (though this requires interface admins, not sysops) --Lucas Werkmeister (talk) 16:19, 27 September 2019 (UTC)

I've removed the style, but left the comment because it seems to apply to the next style too. I think that one could probably be removed too but I wasn't sure. - Nikki (talk) 18:11, 27 September 2019 (UTC)

Sidebar cleanup

{{Edit request}} Please add the code #p-coll-print_export { display: none; } to Mediawiki:Common.css, in order to hide the "Print/export" section of the sidebar, which isn't needed on Wikidata. (Previous: Wikidata:Project_chat/Archive/2020/01#Sidebar_cleanup, MediaWiki talk:Sidebar#Sidebar cleanup.) --Yair rand (talk) 20:29, 18 February 2020 (UTC)

@Yair rand:  Done Mahir256 (talk) 20:46, 18 February 2020 (UTC)

Responsive image

{{Edit request}} Could you add the following class please, to use on a wikiproject page.

/* To make images responsive */
.res-img img {
	max-width:100%;
	height:auto;
}

Thanks. Ayack (talk) 19:37, 7 March 2020 (UTC)

@Ayack: Please use TemplateStyles instead. Common.css is much more inflexible: you need such edit requests (TemplateStyles pages are basically freely editable) and doesn’t work everywhere (Common.css doesn’t load on mobile, i.e. https://m.wikidata.org/, where this rule would be the most needed). If you need help for TemplateStyles, feel free to ask me. —Tacsipacsi (talk) 21:29, 7 March 2020 (UTC)

@Tacsipacsi: Thanks, I've just created Template:Responsive Image and it's working fine. Ayack (talk) 08:41, 9 March 2020 (UTC)

Edit request - show only to admins

{{Edit request}}

In MediaWiki:Common.css, please add

.sysop-show {
	display: none;
}

In MediaWiki:Group-sysop.css, please add

div.sysop-show,
p.sysop-show {
  display: block !important;
}
span.sysop-show,
small.sysop-show {
  display: inline !important;
}
table.sysop-show {
  display: table !important;
}
li.sysop-show {
  display: list-item !important;
}

This will allow hiding things, like block links, from non-sysops. Thanks, --DannyS712 (talk) 21:34, 11 May 2020 (UTC)

The !important;s don't seem to be necessary? --Yair rand (talk) 06:35, 12 May 2020 (UTC)

They are needed to override the display-none --DannyS712 (talk) 09:50, 12 May 2020 (UTC)

@DannyS712: The selectors are more specific, because of the tag selector. They override by default. --Yair rand (talk) 20:28, 12 May 2020 (UTC)

@Yair rand: this was copied from en.wp, where these have !important, in order to override inline-styles. This often happens with collapsible content which uses inline styles (or used to? don't remember). TheDJ (talk) 10:34, 15 May 2020 (UTC)

I do not really see the point for these classes. As much as I am aware, only Template:Checkuser and Template:Checkip use them currently—and they do so in a way that the template would look somewhat broken if we were to make the proposed changes. Am I missing something here, e.g. usage by MediaWiki itself for instance? (@DannyS712 in particular, but input from others is also appreciated.)

Thus I tend to close this as "not done", in order to keep things simple and to avoid introducing more legacy CSS that is potentially difficult to get rid of in the future again. —MisterSynergy (talk) 23:52, 25 October 2021 (UTC)

There aren't any uses by MediaWiki itself that I'm aware of. My reason for the request was to hide links from users that cannot use them, like checkuser links from non-checkusers and block links from non-admins. If this is going to be approved I'll figure out fixing those templates mentioned. I don't think adding this would be "legacy CSS" because its new, and the reason for having it will apply equally in the future. DannyS712 (talk) 02:09, 26 October 2021 (UTC)

• I understand the reason why you have requested it. Question is whether this super specific use case should find its way into the project-wide CSS definition. I am not convinced at this point, but let’s discuss.
• Basically all locally defined CSS (as well as .js) is legacy code, from the moment on when it is introduced to the project. These things may break in unexpected ways since the software in continuously being developed, and thus we regularly need to keep an eye on it.
• Do we have other templates/pages that might use .sysop-show which do not do so yet? This would not be surprising, given that the class is not effective yet.
• What do we do with mobile interfaces? MediaWiki:common.css does not load there, but a consistent behavior is certainly desirable.
• What do we do with other group-specific content? The templates listed above for instance have checkuser-specific links that *could* be treated this way using MediaWiki:Group-checkuser.css for instance. Once starting to think about this, there is potentially quite some content which is group-specific, but nevertheless shown to all users for years now.
• Once we decide that we want to go this way, we need to figure out whether the excessive use of !important is really necessary here.

So, we need a more detailed game plan here. —MisterSynergy (talk) 08:39, 26 October 2021 (UTC)

I think the cleanest solution would be using TemplateStyles with a rule like body:not(.group-sysop) .cuEntry-blocklink { display: none; }—unfortunately, no such class exists currently. Maybe it should be suggested on Phabricator? —Tacsipacsi (talk) 11:56, 26 October 2021 (UTC)

Hiding the main page title

@Ladsgroup: Unfortunately this doesn’t work across languages, for example with German interface now the page title does appear. Maybe we should switch to the way monolingual wikis handle main pages, i.e. treating only Wikidata:Main Page as a main page (although many of the other pages in that CSS rule still exist as separately maintained main pages, so they should be merged into the multilingual Wikidata:Main_Page before this change), but in the short term, I suggest reverting this edit. —Tacsipacsi (talk) 23:35, 11 January 2022 (UTC)

@Tacsipacsi you need to create MediaWiki:Mainpage-title/de as an empty page and that would fix it for German but not others. I reverted it now. Amir (talk) 04:16, 12 January 2022 (UTC)

Styling Deprecated/Preferred Ranks

I propose we add the following

.wb-deprecated { /* deprecated claims with red-ish background */
    background-color: #FFE0E0;
}
.wb-preferred { /* preferred claims with green-ish background */
    background-color: #E0FFE0;
}

to make it easier to notice the ranks of items. Code taken from [1] which also shows what it would look like. We could change the exact colors used if we want. I'm also mentioning this at Wikidata:Project Chat. BrokenSegue (talk) 19:43, 15 January 2022 (UTC)

Maybe better would be "#ffdbdb" for deprecated and "#e0f5eb" for preferred but it doesn't matter that much. BrokenSegue (talk) 19:53, 15 January 2022 (UTC)

•  Support but make it fairly pale please — Martin (MSGJ · talk) 20:31, 15 January 2022 (UTC)
•  Support This proposal seems to be a good idea to make it easier to see wich rank a statement actually has. --Ameisenigel (talk) 20:36, 15 January 2022 (UTC)
•  Support Oh, I'd love that! This would be very useful indeed.Vojtěch Dostál (talk) 21:20, 15 January 2022 (UTC)
•  Support I agree very much with the motivation. --Epìdosis 21:29, 15 January 2022 (UTC)
• See phab:T198907. One issue to consider is phab:T209138.--GZWDer (talk) 04:45, 16 January 2022 (UTC)
•  Support Without this change, it's hard to see what is deprecated or not. Also please make it a bit pale. Infrastruktur (talk) 09:25, 16 January 2022 (UTC)
•  Strong support —Eihel (talk) 15:51, 16 January 2022 (UTC)

 Done [2]. Multichill (talk) 10:45, 16 January 2022 (UTC)

Example (deprecated and preferred): Q250763 —Eihel (talk) 17:33, 16 January 2022 (UTC)

•  Comment It looks odd to me. This way some value is more prominent only because statement happens to have multiple values and rank distinction happens to be appropriate for this statement. While other statements, where best ranking value has normal rank, are sort of arbitrarily less prominent. Value with deprecated rank could be less prominent than other values, not the other way around. Maybe this could be implemented as a (non-default) gadget instead? 2001:7D0:81DA:F780:C53C:B715:B942:37B2 20:11, 16 January 2022 (UTC)
  • I was already using a custom user CSS style to opt-in. I sort of think making this opt-out makes sense (using your own custom CSS). It makes sense for these to be more distinctive for new users. BrokenSegue (talk) 04:08, 17 January 2022 (UTC)

For new users in particular? I'd rather say they are less likely to know anything about ranks, and ranks necessarily aren't among first things they should learn about. They may or may not figure that colours have got something to do with small symbols on the left, but either ways it's hardly intuitive and there's no legend for colours. Also opting out is sort of tricky for new or less experienced users that aren't logged-in users. Generally, I think it'd make more sense for all users if all best ranking values (either preferred or normal rank) would be equally prominent (discussed a little in phab:T87327). 2001:7D0:81DA:F780:3407:A0ED:A73B:CE14 08:42, 17 January 2022 (UTC)

I've already customized my common.css to have different colors for rank icons which is much less intrusive. How can I get back "normal" background color please? (ie. white) Thanks. Ayack (talk) 09:17, 17 January 2022 (UTC)

• • I don't understand this change. Should we now select for every statement one best value so that an item becomes all green? In this issue the sorting was most important, the best statement on top would be expected behaviour. I don't understand that instead of that we now have background colors marking some properties as important. This is not great for presentations and screenshots. --Hannolans (talk) 10:40, 17 January 2022 (UTC)
  •  Comment +1. Generally, I'm in favour of making the ranks of statements more recognisable by applying additional styling instead of just relying on those tiny arrows (that shouldn't require two clicks to switch ranks BTW), but I think that the choice of colours is less-than-ideal. New users might be mislead into thinking that "green" = good and therefore every statement has to be green. Instead, it might be better to choose a different set of colours and maybe style normal-rank the same way as high-rank if there are no statements with high-rank (i.e. what's available using wdt:* in WDQS is highlighted). --Nw520 (talk) 10:51, 17 January 2022 (UTC)
    • Another note: This is quite the major change to the user interface and IMHO should haven been brought up to discussion in an RFC or at least announced in the several language-specific village pumps + weekly summary before implementing it. --Nw520 (talk) 11:00, 17 January 2022 (UTC)
      • I agree that maybe this was a bit hasty (I would've waited at least a week and notifying other languages would've been good). But I find that RfCs on here tend to go on... indefinitely. BrokenSegue (talk) 15:55, 17 January 2022 (UTC)
        • Come on guys. This is a Wikimedia wiki, not a corporate documentation system. Be bold! Nothing would have changed if I deployed it a couple of days later. Now we're getting useful feedback so we can improve further, almost like a wiki! Multichill (talk) 16:44, 17 January 2022 (UTC)
• I’m afraid this change has exacerbated T285694 (see comment): linking to a deprecated or preferred statement (example) can now make the property completely invisible, because the colored background covers it. --Lucas Werkmeister (WMDE) (talk) 10:57, 31 January 2022 (UTC)

  That can be fixed by adding transparency. I tried changing the deprecated background color to "#FFE0E077" and it became visible again. We should probably change it to something with transparency. BrokenSegue (talk) 16:17, 31 January 2022 (UTC)

  Looks like this was fixed with Special:Diff/1573297562. Lucas Werkmeister (WMDE) (talk) 10:04, 7 February 2022 (UTC)

Other styling options

• This is just my opinion. I definitely  Support the idea of styling deprecated/preferred ranks, but as an option, it might be better to use multi-colored icons (see here) rather than a fully colored background. Regards Kirilloparma (talk) 12:17, 16 January 2022 (UTC)

  Personally I think just the colored icons are too subtle. Personally I think deprecated statements should be crossed out using strike-through and preferred should be bolded. But I worry about bike shedding this too much. BrokenSegue (talk) 15:48, 17 January 2022 (UTC)

•  Support the multi-colored icons. Ayack (talk) 15:53, 17 January 2022 (UTC)

  +1 for the colored icon : more visible and less surprising for "lambda users" Bouzinac ^{💬●✒️●💛} 12:45, 19 January 2022 (UTC)

•  Support. This would be an improvement to the original situation without being as intrusive, so to speak, as the new color scheme. Thierry Caro (talk) 09:29, 22 January 2022 (UTC)

I agree that the current red and green is maybe a bit too much. Just the icons makes it too hard to spot it and basically reverts to the previous situation. How about we only give the value a color? That makes it more visible, but it's less surprising. See User:Multichill/common.css to test it yourself. I watered down the colors (more white) to make it less in your face, but still fairly easy to see. Multichill (talk) 12:04, 23 January 2022 (UTC)

i would support moving to this paler color. I'm also fine moving to just the value. I don't feel super strongly about it all though. BrokenSegue (talk) 23:35, 23 January 2022 (UTC)

• From some of the comments, I got the impression that some even frequent contributors didn't even notice ranks before. As we had icons before and that didn't work, I don't see any benefit to use that.

Still, the current approach can be improved: maybe gray for deprecated rank? --- Jura 11:46, 29 January 2022 (UTC)

FWIW, I’ve used preferred and deprecated background coloring for 4 years in my stylesheet. --Mormegil (talk) 17:58, 1 February 2022 (UTC)

Add Noto Nastaliq Urdu as font for Urdu and Punjabi Shahmukhi (pnb) text labels

This font supports characters used which are not visible otherwise. See this lexeme for example: https://www.wikidata.org/wiki/Lexeme:L680188 ناࣇ

For a full Nastaliq font fallback list that can be used, see https://en.wikipedia.org/wiki/Template:Uninastaliq

--Middle river exports (talk) 20:18, 29 June 2022 (UTC)

I checked Noto Nastaliq Urdu and it doesn't contain that character...? Specifying a font won't do anything either unless you already have that font - we can't provide missing fonts. For that, you'll need to make a feature request for the Universal Language Selector.

In general, providing a list of fonts for a language doesn't seem like something that really belongs here - we shouldn't need to customise the defaults. If we do, that seems like a bug in MediaWiki or Wikibase (the extension that Wikidata uses) that should be reported, because either MediaWiki's font settings are inadequate and any wiki which tries to display our data will have the same problem, or Wikibase is overriding MediaWiki's fonts in a way that it shouldn't.

- Nikki (talk) 04:56, 30 July 2022 (UTC)

I missed this response - Noto Nastaliq does contain the character, but it renders it poorly (see https://github.com/notofonts/nastaliq/issues/16 ).

I realized this wasn't the place to change this and now there are pending changes to the font options in ULS (Gulzar is the best open source Nastaliq font I've been able to find) Middle river exports (talk) 07:08, 17 September 2022 (UTC)

pnb Wikidata logo

{{Edit request}} Could the image at [3] be added as a custom language logo for Punjabi Shahmukhi (pnb), like the Bengali and Urdu ones? I have been working on translating more of the main page and user interface to Punjabi and this would be a better fit in that context. --Middle river exports (talk) 07:17, 17 September 2022 (UTC)

@Middle river exports:  Done Mahir256 (talk) 07:49, 17 September 2022 (UTC)

pa Wikidata logo

{{Edit request}} This request now is the for the image at Wikidata=logo-pa.svg to be used for language code pa / Punjabi Gurmukhi. This logo was made 5 years ago by User:Satpal Dandiwal but never included in this CSS. (I was aware of this earlier when I requested pnb, but wanted to double check if the common spelling of "data" in Gurmukhi was really "ਡਾਟਾ" as opposed to "ਡੇਟਾ" since the Translate Wiki strings confusingly use a mix of both. It turns out ਡਾਟਾ really is the main spelling, and is used about 3 times as much in Gurmukhi despite ڈاٹا constituting a rare fraction of spellings of the word in Shahmukhi + Urdu.) --Middle river exports (talk) 18:20, 18 September 2022 (UTC

This one will be covered by T323734. Stang^★ 23:52, 23 November 2022 (UTC)

Done. Stang^★ 15:43, 24 November 2022 (UTC)

Request to add font-synthesis: none style rule

It is requested that an edit or modification be made to this protected page.

The page has been added to Category:Wikidata protected edit requests.

Administrators: Please apply <nowiki> or {{Tl}} to the tag after the request is fulfilled.

Fulfill this request after you checked that it does not contain evil code

Described here font-synthesis on MDN The CSS rule to add:

   html, body {
      font-synthesis: none !important;
   }

All this does is it tells the browser not to force rendering of glyphs which are not contained in the font rendering them. This should prevent the presence of italic styling from breaking the rending of Arabic script text, for example. This property is supported by most browsers at this point and it seems appropriate for a multilingual site like Wikidata. عُثمان (talk) 03:57, 21 November 2022 (UTC)

@عُثمان: I suggest to file a task at Phabricator. Stang^★ 23:51, 23 November 2022 (UTC)

!important is rarely ok, and I wouldn't support it here. The general request looks ok. Izno (talk) 21:39, 28 November 2022 (UTC)

Remove messagebox

{{Edit request}} I've removed the use of .messagebox such that it can be totally removed from Common.css. It has Module:Message box-based replacements where necessary for future editors.

Template talk:Checkuserblock 2#Edit request to remove messagebox needs to be done first.

This would remove lines 113 to 138:

/**
** Messagebox templates
** Imported from [[en: MediaWiki:Common.css]] on 2012-11-24
**/
.messagebox {
	border: 1px solid #a2a9b1;
	background-color: #f8f9fa;
	width: 80%;
	margin: 0 auto 1em auto;
	padding: .2em;
}
.messagebox.merge {
	border: 1px solid #c0b8cc;
	background-color: #f0e5ff;
	text-align: center;
}
.messagebox.cleanup {
	border: 1px solid #9f9fff;
	background-color: #efefff;
	text-align: center;
}
.messagebox.standard-talk {
	border: 1px solid #c0c090;
	background-color: #f8eaba;
	margin: 4px auto;
}

Izno (talk) 21:43, 28 November 2022 (UTC)

@Izno: Sorry for the late reply! One problem, is Template:Documentation_subpage/en this page needs to be updated as well? Actually I'm not sure what that page is about... Stang^★ 23:50, 27 February 2023 (UTC)

@Stang, I don't know either. It doesn't look to be necessary with however translation functions these days, for example in English Template:·/doc displays with the expected main template. You can probably delete it. Izno (talk) 23:56, 27 February 2023 (UTC)

@Izno:  Done. Stang^★ 00:03, 28 February 2023 (UTC)

Main page title hiding

@Nikki: Unfortunately phab:T298715 doesn’t work as expected on multilingual wikis. For example, Wikidata:Degemer didn’t use to have a title, but now it has. While many (most?) translated main page names redirect to Wikidata:Main Page, some don’t. I’ve created a query that lists the pages mentioned in the previous version and whether they’re redirects; please restore the CSS rules that refer to non-redirect pages. Thanks in advance! —Tacsipacsi (talk) 22:46, 26 February 2024 (UTC)