Template talk:Pre

message: Just add this to your user CSS:

/* Make preformatted sections overflow with a scrollbar instead of uglies */
pre {
    overflow: auto;
    width: auto;
}

— Omegatron 01:13, 16 May 2006 (UTC)
thread_title:  Making all ''pre''s autoflow 

message: I wonder whether it would be particularly bad if the name Template:Pre was usurped by the current Template:Pre2?
 generates <pre>s, but with wrapped text, or a scrollbox, depending on the settings/parameters. It's quite new, but it would be easier to remember if it only had the name . The reason I like it is that I use the modern skin, and so , as it is at the moment, shows <pre> differently to normal. It's still a very useful template though, well done on making it! I'm wondering if it could be moved to a different name?
All comments very much appreciated; thanks, Drum guy (talk) 23:16, 13 June 2008 (UTC)
replies: text: I've imported Pre2 in my wiki (http://neurov.is/on), since it seemed cleaner at first glance than Pre.  Thanks for creating it!  I prefer Pre2 and I think it would be worthwhile to consider replacing Pre with it, but I don't know enough about the two to really recommend doing so.  Would there be any backwards compatibility issues? JonathanWilliford (talk) 14:05, 13 August 2009 (UTC)
thread_title:  Maybe usurp the name Template:Pre? 

message: A recent change to the styling of the  element means that this template no longer does what it claims to do:
is not at all similar to
This Pre-format
can look
like this.
See related post at MediaWiki talk:Common.css#Double border. --Redrose64 (talk) 09:16, 1 August 2014 (UTC)
replies: text: Why is this template using  in the first place? That is an inline tag. -- User:Edokter  10:15, 1 August 2014 (UTC)
replies: text: Then why ? That's also an inline element. --Redrose64 (talk) 13:51, 1 August 2014 (UTC)
replies: text:  There are several elements in HTML5 that we might expect a browser to render as mono-spaced, but which have different semantic meanings. The relevant document is http://www.w3.org/TR/html5/text-level-semantics.html and it defines:  as "a fragment of computer code";  as "user input"; and  as "(sample) output from a program". Semantically, you can't determine the correct tag here as it would depend on the content supplied to the template. I'd have thought that a container with its font-family set to monospace would be the general solution here. --RexxS (talk) 14:42, 1 August 2014 (UTC)

text: I tried , but that disables all template code inside. Any way around that? -- User:Edokter  15:12, 1 August 2014 (UTC)
replies: text:  It looks like the  is only being used to supply the monospaced font. In the , I've removed the  and applied font-family: monospace; font-size:1.3em; to the container. Looking at Template:Pre/testcases, it seems to do the job. See what you think? --RexxS (talk) 15:54, 1 August 2014 (UTC)
replies: text: I want to use  so all the inline styling can be removed. -- User:Edokter  16:15, 1 August 2014 (UTC)

text: I stole a trick from , now it looks much better. -- User:Edokter  16:29, 1 August 2014 (UTC)
replies: text: Yesss... what does the empty  do? --Redrose64 (talk) 16:47, 1 August 2014 (UTC)
replies: text: Apparently, it prevents the pre tag from kicking in (and disabling all the template code) before being transcluded. -- User:Edokter  18:10, 1 August 2014 (UTC)
thread_title:  Double border