Template talk:Col-2

Example:

Wikipedia:tutorial
This code makes the last page of the tutorial fit within a square screen:

That this works implys that 50% does not take into account the border, and therefore probably should be 47% instead --Chuck Marean 17:04, 13 October 2006 (UTC)

Edit request
Please replace by 16@r 22:09, 19 October 2007 (UTC)


 * ✅ Done, but I changed it to   instead, since it appears that that was your intent given the other editprotected requests you made. :)  Nihiltres ( t .l ) 14:15, 20 October 2007 (UTC)

Hello. It would be better to changed the above code into:

And then move the page Col-begin/doc to Template:Col-begin/doc. Greetings --Tlustulimu (talk) 14:20, 11 January 2008 (UTC)

Is the line break in >
 * width= creating extra space? If so, this needs to be removed.174.3.121.27 (talk) 03:52, 31 May 2010 (UTC)

interwiki
editprotected
 * ru:Шаблон:Col-2
 * dz:Template:Col-2 --Impro (talk) 06:21, 19 August 2010 (UTC)


 * Disabling. Interwiki links on the templates go on the /doc page, which is not protected. The Russian link at least is already present. Chris Cunningham (user:thumperward: not at work) - talk 14:57, 19 August 2010 (UTC)

Use CSS
Could someone update this template to [//pt.wikipedia.org/w/index.php?title=Predefini%C3%A7%C3%A3o:Col-2&diff=32827290 use CSS instead of deprecated presentational attributes]? Helder 13:13, 3 November 2012 (UTC)
 * Yes check.svg Done see . Strictly speaking, these three attributes are obsolete ([//www.w3.org/TR/html5/obsolete.html#attr-tdth-align ]; [//www.w3.org/TR/html5/obsolete.html#attr-tdth-valign  ]; [//www.w3.org/TR/html5/obsolete.html#attr-tdth-width  ]) in HTML 5, not deprecated: the difference is that browser writers are under no obligation to support obsolete features, but should support deprecated features for the time being, for backward compatibility. All three were valid in HTML 4, but only   was [//www.w3.org/TR/html4/struct/tables.html#edef-TD marked as deprecated]. -- Red rose64 (talk) 15:05, 3 November 2012 (UTC)

Extra tag?
Is that tag really needed? It seems this is removed by Tidy (and maybe it breaks if Tidy is disabled). Helder 13:13, 3 November 2012 (UTC)
 * I was wondering what its purpose is. Not knowing, I've left it alone. -- Red rose64 (talk) 15:05, 3 November 2012 (UTC)
 * FYI: Long note follows, but just in case anyone is interested.
 * The extra  causes some unintentional behavior today. It invalidates the last attribute in the preceding wikitable code.
 * This affects a common invocation of  where the style attribute in   is not shown.
 * Here's a simple example you can test in Sandbox:
 * View the HTML. Note that the &lt;table> says role="presentation" but does not have a style attribute
 * Now try this: (note the whitespace) between  and
 * View the HTML. Note that the &lt;table> says role="presentation" and has a style attribute
 * The reason for the difference is because Template:Col-begin ends with a style attribute
 * When  is appended, the following string is generated:
 * This text is treated by the Xml Attribute parser in Sanitizer.php as an invalid attribute (It stops at the whitespace, not the close quote)
 * As a result, the parser strips the entire style attribute.
 * I'm going to guess that the &lt;p> tag was put in to force a new line for the next line's "| style="width:50%; ". This would have occurred while MediaWiki was putting in code to automatically prepend "\n" to any template that starts with "|", "*", etc..
 * This makes the &lt;p> tag unnecessary to its original purpose, though removing it today, would cause pages to render worse.
 * For example, Supreme Court of the United States would have a large gap between "See also" and the first list. This gap would be introduced by the currently suppressed style: "border-collapse: collapse;". You can test it by adding/removing a space with the following:
 * This text is treated by the Xml Attribute parser in Sanitizer.php as an invalid attribute (It stops at the whitespace, not the close quote)
 * As a result, the parser strips the entire style attribute.
 * I'm going to guess that the &lt;p> tag was put in to force a new line for the next line's "| style="width:50%; ". This would have occurred while MediaWiki was putting in code to automatically prepend "\n" to any template that starts with "|", "*", etc..
 * This makes the &lt;p> tag unnecessary to its original purpose, though removing it today, would cause pages to render worse.
 * For example, Supreme Court of the United States would have a large gap between "See also" and the first list. This gap would be introduced by the currently suppressed style: "border-collapse: collapse;". You can test it by adding/removing a space with the following:
 * This makes the &lt;p> tag unnecessary to its original purpose, though removing it today, would cause pages to render worse.
 * For example, Supreme Court of the United States would have a large gap between "See also" and the first list. This gap would be introduced by the currently suppressed style: "border-collapse: collapse;". You can test it by adding/removing a space with the following:

Template-protected edit request on 1 August 2018
Use of   generates a Lint Error.

Code should be replaced with something like:


 * style="width:50%; text-align:; vertical-align:;" |

}} ~

ShakespeareFan00 (talk) 10:37, 1 August 2018 (UTC)
 * Red information icon with gradient background.svg Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. See my comment at Template talk:Col-break. I'm guessing the same applies here. StevenJ81 (talk) 16:56, 1 August 2018 (UTC)

Inter-language links
I have a doubt regarding the doc file of this template. Please check whether the inter language links present on the doc file needs to be removed from the doc file and added to wikidata or not. Adithyak1997 (talk) 06:20, 2 October 2018 (UTC)

Using with multi-level bulleted lists
Is there a proper way to use this template with multi-level bulleted lists that avoids any of the WP:LISTGAP problems discussed at Talk:2024 in combat sports. I tried a fix here that seems to help mitigate the problem, but might not be the best way to approach this. -- Marchjuly (talk) 00:40, 7 May 2024 (UTC)