Editing Template talk:Proposal outcome
From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
Should we add a parameter for appeals (and other things along those lines)? The [[MarioWiki:Appeals]] page looks awfully unprofessional with the old Comic Sans font that doesn't have the template. {{User:Roy Koopa/sig}} 20:19, 24 May 2016 (EDT) | Should we add a parameter for appeals (and other things along those lines)? The [[MarioWiki:Appeals]] page looks awfully unprofessional with the old Comic Sans font that doesn't have the template. {{User:Roy Koopa/sig}} 20:19, 24 May 2016 (EDT) | ||
:No. We should make a new template if we create a template for appeal outcomes. In fact, this discussion should be moved to [[MarioWiki talk:Appeals]]. --{{User:Wildgoosespeeder/sig}} 20:30, 24 May 2016 (EDT) | :No. We should make a new template if we create a template for appeal outcomes. In fact, this discussion should be moved to [[MarioWiki talk:Appeals]]. --{{User:Wildgoosespeeder/sig}} 20:30, 24 May 2016 (EDT) | ||
| Line 5: | Line 4: | ||
== Remove typeface property from this template == | == Remove typeface property from this template == | ||
{{ | {{TPP}} | ||
Currently, this template uses the Verdana typeface (or font) set by <code>font-family</code> property, which appears to the chosen by some people in [[MarioWiki_talk:Proposals/Archive_1#Comic_Sans:_yea_or_nay.3F|this discussion]], but I don't think it makes sense to forcibly use it on this (and possibly other templates) when both the [https://files.catbox.moe/474d9p.png MonoBook] and [https://files.catbox.moe/ux34ou.png Vector] skins defaults the body text to <code>sans-serif</code>, which would be the sans-serif typeface set in the browser (usually defaults to Arial), anyway.<ref group="n">I am aware that most of MonoBook's user interface does use Verdana, but this still look out of place compared to body texts.</ref> On most mobile devices, this property also has no effect (both in [https://files.catbox.moe/puxg3x.png default mobile view] and [https://files.catbox.moe/iogej8.png desktop view]) as they don't have Verdana typeface available and thus falls back to the <code>sans-serif</code> typeface. This proposal thus would decide whether to change the <code>font-family</code> property to <code>sans-serif</code> for consistency across body texts. | Currently, this template uses the Verdana typeface (or font) set by <code>font-family</code> property, which appears to the chosen by some people in [[MarioWiki_talk:Proposals/Archive_1#Comic_Sans:_yea_or_nay.3F|this discussion]], but I don't think it makes sense to forcibly use it on this (and possibly other templates) when both the [https://files.catbox.moe/474d9p.png MonoBook] and [https://files.catbox.moe/ux34ou.png Vector] skins defaults the body text to <code>sans-serif</code>, which would be the sans-serif typeface set in the browser (usually defaults to Arial), anyway.<ref group="n">I am aware that most of MonoBook's user interface does use Verdana, but this still look out of place compared to body texts.</ref> On most mobile devices, this property also has no effect (both in [https://files.catbox.moe/puxg3x.png default mobile view] and [https://files.catbox.moe/iogej8.png desktop view]) as they don't have Verdana typeface available and thus falls back to the <code>sans-serif</code> typeface. This proposal thus would decide whether to change the <code>font-family</code> property to <code>sans-serif</code> for consistency across body texts. | ||
<references group="n"/> | <references group="n"/> | ||
| Line 14: | Line 12: | ||
=== Change the <code>font-family</code> property to <code>sans-serif</code> (support) === | === Change the <code>font-family</code> property to <code>sans-serif</code> (support) === | ||
=== Keep Verdana (oppose) === | === Keep Verdana (oppose) === | ||
=== Comments === | === Comments === | ||
what benefit would this change have, besides a bit more font consistency? {{User:EvieMaybe/sig}} 11:42, February 20, 2025 (EST) | what benefit would this change have, besides a bit more font consistency? {{User:EvieMaybe/sig}} 11:42, February 20, 2025 (EST) | ||
:Per Evie. I feel like it doesn't matter that much in the grand scheme of things. The Proposal outcome template is supposed to stand out and easily convey... well, the outcome of | :Per Evie. I feel like it doesn't matter that much in the grand scheme of things. The Proposal outcome template is supposed to stand out and easily convey... well, the outcome of am ended proposal, not necessarily to be consistent with the rest of the body text.<br>Also, I would like if you set out an example of how the template's text would look like with your proposed changes applied (like, with a screenshot or something). {{User:Arend/sig}} 12:07, February 20, 2025 (EST) | ||
