Use for code[edit]

The documentation for this template currently says it should not be used for inline source code, but I and others have been using it for this purpose because <code> is so ugly. What should I do to get this changed? QVVERTYVS (hm?) 10:45, 15 March 2015 (UTC)[reply]

Discuss at WP:VPT. -- Gadget850 talk 14:48, 8 May 2015 (UTC)[reply]
Proposal at Wikipedia:Village pump (proposals)#Change formatting of inline code snippets. QVVERTYVS (hm?) 15:23, 8 May 2015 (UTC)[reply]

Template-protected edit request on 3 November 2017[edit]

Why is "monospace" listed twice? List it once. Anomalocaris (talk) 20:40, 3 November 2017 (UTC)[reply]

 Not done Looking at the edit summaries in the history of the template, it seems that this is needed to make the template work properly in the Chrome browser. -- John of Reading (talk) 20:56, 3 November 2017 (UTC)[reply]
John of Reading Ah, so! Thanks for your reply. —Anomalocaris (talk) 22:13, 5 November 2017 (UTC)[reply]
I can confirm that as of this timestamp this (harmless) CSS hack is still required.  — SMcCandlish ¢ 😼  05:32, 28 July 2018 (UTC)[reply]

Bad substitution[edit]

Izno, a search for the emitted templatestyles shows that this template has been substituted ca. 35 times since it was converted to use templatestyles. do we need to add some ((ifsubst)) or unsubst logic to avoid unclean substitution? Frietjes (talk) 16:54, 23 October 2018 (UTC)[reply]

@Frietjes: I'd say so -- if substed, should not output the templatestyles tag. The user in question should be told not to use the template directly as a followup if he wants to retain monospaced text. --Izno (talk) 17:01, 23 October 2018 (UTC)[reply]
@Usernamekiran: Frietjes (talk) 17:03, 23 October 2018 (UTC)[reply]
@Frietjes and Izno: Thanks. I am not exactly sure what we are discussing here. If I'm guessing correctly, then we are talking about substituting mono template. In that case, I've stopped doing it a while ago. Kindly see User talk:Usernamekiran/Archive 6#Are you substing Template:Mono in your signature? For current situation. If I need to make changes in my signature, kindly let me know; and I will do it accordingly usernamekiran(talk) 19:13, 23 October 2018 (UTC)[reply]
Usernamekiran, great, no action needed at this point in time. Frietjes (talk) 19:39, 23 October 2018 (UTC)[reply]
@Izno and Frietjes: currently sporkbot is unsubstituting templatestyles. special:diff/865576272. He even went through my archives. —usernamekiran(talk) 23:19, 24 October 2018 (UTC)[reply]
Usernamekiran, yes, I made the request per WP:TemplateStyles (Substituting a template which uses TemplateStyles leaves the <templatestyles /> tag in the resulting code, which may be confusing and negates many of the benefits of using TemplateStyles in the first place.), so the issue here is resolved, assuming no one else tries to substitute it. for ((smallcaps)) there is now ((ifsubst)) to prevent unclean substitution. we could do that here as well. Frietjes (talk) 23:22, 24 October 2018 (UTC)[reply]

Wikilinks and external links[edit]

This template does not work around or inside wikilinks and external links.

Anomalocaris (talk) 19:41, 16 May 2021 (UTC)[reply]

I had forgotten that I had posted the above, and I just edited and removed a bunch of edits to this talk page based on the belief that the template has problems around <nowiki>...</nowiki> tags. I now believe the problem related to wikilinks. The problem with wikilinks and external links remains and should be fixed. —Anomalocaris (talk) 04:25, 13 July 2022 (UTC)[reply]

Repetition in TS style[edit]

Just curious. Currently, Template:Mono/styles.css has

 font-family: monospace, monospace;

Is there a reason for this repetition? -DePiep (talk) 18:15, 19 November 2021 (UTC)[reply]

@DePiep: Yes, see the information in WP:MONO linked in the comment above. Basically some browser threat font: family: monospace; specially and reduces the font size. monospace, monospace works around this. I'm not sure if this still is a problem in newer browsers. See also T176636. -- Tholme (talk) 15:15, 15 March 2022 (UTC) T176636[reply]