Template talk:No vote feature link

Text no longer readable

@Cyton: The text "The proposal <XXX> was built without a vote and the tagging is widely established based on this proposal. The Feature Page for the proposal <XXX> is located at" is no longer readable in normal mode since your last change here, as it now is white on a very light background. Could you please fix this? --Hufkratzer (talk) 11:27, 16 February 2026 (UTC)

How about now?

Strange, I suspect something is not working as expected with your combination of device (-type), browser, css, os, version, specific wiki skin you use, some other addon, something like that.

I use the CSS variable "color-base", documented here: https://doc.wikimedia.org/codex/latest/design-tokens/color.html
Sometimes some of them aren't available on some wikis, I do not know why.

As a test, what color is the background of the following red word?

Beispielwort

If it's the same as the rest of the page, that variable isn't available for you, hence the fallback (second argument) of the var was used, where (previously) there was only white.
If it's black on white (light-mode) or white on black (darkmode), then it should have worked as expected, and I'd be more confused.

In any case, it was my fault for not thinking of also putting a light-dark wrapped value-pair in the var().

–Cyton (talk) 12:12, 16 February 2026 (UTC)

The background color of "Beispielwort" is the same as the rest of the page in Firefox, Chrome and Edge on Windows 10. Meanwhile you have improved the template and its text is readable again; thanks. --Hufkratzer (talk) 16:25, 16 February 2026 (UTC)

I checked it too and it seems not to be a browser issue but a wiki skin one. It works as inteded (black on white page) with new "Vector 2022" and "Minerva" / "mobile view" (either Firefox and Brave browser), but not with the standard "legacy" skin. --Chris2map (talk) 16:33, 16 February 2026 (UTC)

Oh, that … makes sense, unfortunately.

Makes me think; should there be some kind of workaround?
Maybe copy paste all the variables from that codex color page over here, or use a template for these default colors, each with a sensible fallback for light- and darkmode? Is there such a thing already?

Otherwise, any time a variable is used, and I may have done some other edits the same way, this same kind of "bug" will happen there too and also in any future cases.
The nice thing about these variables is that they're just "there", and are part of a working color scheme. If they don't work ...

Benefit of a template would be that amy instances could be chamged at once, a css-variable too, but maybe not by my account. Cyton (talk) 17:09, 16 February 2026 (UTC)