Template talk:Font

Design choice

This template always fills all style parameters with default values. This is inflexible, since these local default may differ from the globally defined defaults. Furthermore it will create undefined effects if several copies of this template are used, because the same property will be specified several times.

Better would be to omit all specifications that are not explicitly given by the invocation.

Instead of

font-family:{{#if: {{{font|}}} |{{{font}}}|sans-serif}}

it should contain:

{{#if: {{{font|}}} | font-family: {{{font}}}}}

et cetera −Woodstone (talk) 05:44, 20 June 2016 (UTC)

I agree, but I imagine that possibly too many current uses of the template may depend on the current behaviour, in which case it would be easier to make a new template with another name than to change this template. --Pipetricker (talk) 10:45, 16 January 2019 (UTC)

I also agree, because the current specification unnecessarily concerts the title font for templates like {{Ordination}} in Pope Tawadros II of Alexandria#Papacy to choose a sans-serif font even though my default font isn't sans-serif. --Esperfulmo (talk) 22:24, 6 May 2023 (UTC)

Template-protected edit request on 18 July 2023

Merge the sandbox into the template. This should introduce the following changes:

1. Positional parameters are supported for every named parameter
2. The title parameter has been removed since it's undocumented and we have the css parameter
3. Every other argument has been reorganized so they don't add any style when the parameter is empty or unspecified Aaron Liu (talk) 00:59, 18 July 2023 (UTC)

 Not done: Unnamed parameters can cause all sorts of trouble, especially when they are mixed with named parameters. What is the rationale for introducing this source of perennial errors into this template? Is there something broken that the requester is trying to fix? – Jonesey95 (talk) 16:15, 18 July 2023 (UTC)