Template talk:Compact TOC/Archive 1

Unused letters

Resolved

 – Done (and then some).

I want the toc not to show unincluded letters! —Preceding unsigned comment added by 77.177.31.102 (talk) 01:16, August 25, 2007 (UTC)

I can probably code that in there, but its usage will be very tedious, something like |j=no|k=no|q=no|v=no|w=no|z=no, and it would have to be manually updated; MediaWiki template and ParserFunction syntax ain't exactly PHP; it can't auto-detect such things. — SMcCandlish [talk] [cont] ‹(-¿-)› 02:35, 27 August 2007 (UTC)

An "az=no" option, and "line1" shorthand

• If CompactTOC8 is poised to emulate/replace all other TOC templates, I think there's at least one feature missing. Currently I have to use {{OnelinerTOC}} like this:

{{OnelinerTOC|notop=y|List|See also|References|External links}}

(I don't display the result here because it would disable the discussion page's own TOC, but the result can be seen at List of mountains in Peru.)

• To emulate it with CompactTOC8, an az=no option would be needed, like this:

{{CompactTOC8|side=yes|nobreak=yes|az=no|custom1=List|seealso=yes|refs=yes|extlinks=yes}}

(I realize I could cancel each letter separately, but that's too much trouble ;-)

• Also, since a non-alphabet linear TOC is a common need for many list articles, maybe there could also be a new shorthand, a "line1" keyword as first param, that would perform exactly the same as the two examples above with just:

{{CompactTOC8|line1|custom1=List|seealso=yes|refs=yes|extlinks=yes}}

(I've not evaluated how complicated it would be to implement this, though.)

— Komusou ^talk @ 20:03, 7 October 2007 (UTC)

That all sounds sensible, but I don't understand why it would be called "line1". — SMcCandlish [talk] [cont] ‹(-¿-)› 17:44, 15 August 2008 (UTC)

PS: CompactTOC8 could easily absorb all the functionality of OnelinerTOC simply by supporting its functions, its named parameters that don't match C'TOC8s but do map to its functionality, and since C'TOC8 doesn't use any unnamed parameters, we can simply reserve them for precisely the function O'l'TOC is doing (i.e. make unnamed parms match to custom1, custom2, etc. — SMcCandlish [talk] [cont] ‹(-¿-)› 18:26, 15 August 2008 (UTC)

Explicit custom

Curently, the template does this with custom1:

Input: custom1 = foo
Output: [[#foo|foo]]

Which is generally good, but wouldn't it be possible to add somthing in to choose where the link is, and what the name is? I found an article where I would want the link to appear as [[#foo|bar]], but it is not possible to do this. I don't think implementing this change would be too difficult:

We add customname1, which when present changes the name of the link.

happypal (Talk | contribs) 18:55, 8 July 2008 (UTC)

Unless I get instruction not to do so, I'll do it in a few days with the varaible names custom1name custom2name and custom3name.happypal (Talk | contribs) 18:57, 8 July 2008 (UTC)

Sounds good to me; the more features the better. The real doozy is going to be making it work across multi-page articles! — SMcCandlish [talk] [cont] ‹(-¿-)› 17:42, 15 August 2008 (UTC)

Numeric list option

It would be cool if it could do numeric lists, to arbitary numbers (i.e. specify a range, like 0-10, or 1-213 or whatever. I've been away from parserfunction code for so long, I can't even remember if this is feasible (other than manually coding it up to a limit of numbers, I mean). — SMcCandlish [talk] [cont] ‹(-¿-)› 18:19, 15 August 2008 (UTC)

Aa - Zz

It's conceivable that some uses will need Aa Ab ... Zy Zz. — SMcCandlish [talk] [cont] ‹(-¿-)› 18:19, 15 August 2008 (UTC)

Border & background removal

One of the only remaining features supported by one or another of the CompactTOC family not supported here is the ability to do away with the border and background; I forget which one has this, but it is used on a lot of "Wikipedia:" namespace pages. — SMcCandlish [talk] [cont] ‹(-¿-)› 18:29, 15 August 2008 (UTC)

Crucial: Multi-page articles

Probably the most-needed upgrade is the ability to work in multi-page list articles. My initial thoughts on this are that there should be:

• apage= ... zpage= (and numpage=, sympage= and numsympage=) where the value would be the page name. Like, I have a big list article that is broken up into three pages. Page 1 contains entries under numsym through K, page 2 is L through P, and page 3 is Q through Z. Page one is FoobarbazquuxA, the second FoobarbazquuxB and the third is FoobarbazquuxC. The code to add would be:
  |numsympage=FoobarbazquuxA|lpage=FoobarbazquuxB|qpage=FoobarbazquuxC
  and it would just work on all three pages, treating everything after the letter specified in a *page as being on the same page until it hits another *page parameter.

• A shorthand, for cases where we want every single letter of the alphabet (or numbers; see feature idea above) to be on its own page, w/o having to manually do it all with apage=, bpage=, etc. Maybe somethng like this: A pagebase= and pageincrement pair, used like this (intended mainly for "Wikipedia:" namespace uses where there would be a page for every single letter; I doubt any list articles are actually that size, though someday they could be), and it would work like:
  |pagebase=Foobarbazquux|pageincrement=alpha
  (with num being the other possible value, for pagenames like Foobarbazquux1, Foobarbazquux2, etc.

Someone might be able to think of a smarter way to do it.

PS: Of course, a tedious work around for multi-page articles with only a few pages would be to do something like
...|l=|p=|...|z=|custom1=L-P|customtarget1=FoobarbazquuxB...
but customname* isn't even implemented yet, much less a customtarget* that could specify a different article entirely.

Ideas? This is actually of some importance to me, because Glossary of cue sports terms is approaching 200K and people are complaining.

— SMcCandlish [talk] [cont] ‹(-¿-)› 18:19, 15 August 2008 (UTC)

Merge

I think it is almost time to go to TfD and get all the lesser templates of this sort merged into this one, and have it renamed to CompactTOC, since it not only will do everything they will, it also has simple default usage. The stumbling block would be to ensure that all parameters of the lesser templates are handled (even if not documented - some might need to be intentionally deprecated by not mentioning them) by this one. — SMcCandlish [talk] [cont] ‹(-¿-)› 18:13, 27 November 2007 (UTC)

Sept. 2007 changes needed documentation

Resolved

 – Documented.

Circeus and someone else have made a bunch of changes recently, and their effects are not reflected in the documentation. — SMcCandlish [talk] [cont] ‹(-¿-)› 19:09, 9 September 2007 (UTC)

They are, I'm pretty sure I didn't forget anything. I added 3 "custom" parameters (+legacy "Sec" for compatibility with other existing templates), and the letter replacement stuff. Am I forgetting anything? Circeus 19:43, 9 September 2007 (UTC)

Looks good, but I would remove the "Sec" stuff from the documentation, so people don't keep using them. — SMcCandlish [talk] [cont] ‹(-¿-)› 17:37, 15 August 2008 (UTC)

New features

I added a couple extra features, and I updated the doc:

• Up to 5 custom tables now.
• Custom name for custom sections:custom1name field. It is possible for the link to appear as:[[#custom1|custom1name]]
• Linking to outside pages is possible, using custom1link field: [[custom1link|custom1]]

If this breaks anything, or if you have any question, please inform me. happypal (Talk | contribs) 08:53, 21 August 2008 (UTC)

Redirect Numbers?

OK, I see how to include an entry for numbers (num=yes), and I see how to redirect letters, but how does one redirect the number entry in the toc to a separate page? I'm trying to build a toc for an article that spans a number of pages, and I'd like to be able to access the number portion from any of those pages. Please specify the syntax. Dawynn (talk) 20:29, 16 December 2008 (UTC)

New parameters, validation & internal comments

10-Jan-2009: New parameters have been added (pre1, pre2, prebreak, sep, ...). The internal coding of the template has been expanded and documented with source-code comments, using the typical HTML form (using "<!-- -->"). Invalid parameters (such as "ref" for "refs" or "ext" for "extlinks") are detected now and rejected. See details below. -Wikid77 (talk) 10-Jan-2009

Header parameters after ABC: custom6 7 8

The new parameters custom6, custom7, custom8 (or Sec6, Sec7, Sec8) allow up to 8 section headers after the ABCDEF links. -Wikid77 (talk) 21:55, 10 January 2009 (UTC)

Header parameters before ABC: pre1 pre2 pre8

The new parameters pre1, pre2, ..., pre7, pre8 (or preSec1, preSec2, ... preSec8) allow up to 8 section headers to be listed before the ABCDEF links. This is totally new. They can be given display-names as pre1name, pre2name (or preSec1name, preSec2name etc.) to conceal a different link name, such as to another article, or an external webpage. So, the total of headers becomes:

Contents: Top pre1 pre2 pre8 A B C D E F custom1 custom2 custom8

Combining the pre1...pre8, with the custom1...custom8, allows up to 16 other header sections to be listed in the TOC. -Wikid77 (talk) 21:55, 10 January 2009 (UTC)

Separator parameter: sep

The new parameter "sep" can set the separator text between the word-headers (not between ABCDEF...). Use "sep=·" to put middots between the header names. Bold middots can be set by putting 3 quotemarks before/after the middot. -Wikid77 (talk) 21:55, 10 January 2009 (UTC)

Prefix break parameter: prebreak

The new parameter "prebreak" can set the break-text after all the pre-listed headers pre1, pre2...pre8 (not between ABCDEF...). Typically, this would be one break-tag as "prebreak=<br>" but could include more text that introduces the line of "ABCDEF...". -Wikid77 (talk) 21:55, 10 January 2009 (UTC)

Validation rejects invalid parameters

For decades, some software procedures have used "parameter validation" to check for problems when passing parameters. Templates can do validation, as well, and now CompactTOC8 does. There is a section of code, at the end of the template, that warns when it finds & rejects invalid parameter names: centre, Top, ref, Ref, ext, extlink, etc. The concept is to have the template check for common typos and say whoa. It works: most invalid parameters will be a few common misspellings. Otherwise, invalid parameters are totally ignored (as typical) and users are left in the dark (neat, huh, ya right). Although some computers act by "No news is good news", today's compu-trash computers think "No news doesn't mean anything, because we ignore the slightest problem, and for years, no one will ever know what went wrong". It doesn't have to be that way, but when parameters are rejected, then text has to be fixed to avoid error messages. It is a design choice to ignore problems, beause often, the error messages are worse than the original problem. Please don't blame any wiki-developers, because unreported errors are rampant in 90% of all websites and poorly designed software, worldwide. Just help to foster parameter and data checking in future templates. -Wikid77 (talk) 21:55, 10 January 2009 (UTC)

non-Latin lists

Is there a horizontal TOC template for lists which are not in the Latin alphabet, for example List of Cyrillic digraphs?

Thanks, kwami (talk) 20:17, 23 April 2009 (UTC)

consistent opening and closing <div> tags

The following section of the template code adds an opening <div style="text-align:???"> tag when the conditional statement evaluates to false, but does not add an opening <div> tag when the conditional statement evaluates to true.

<!-- ----------------------------------- Check name/side-->
#ifeq:{{{name|}}}|no||! {{{name|{{MediaWiki:Toc}}}}}{{#ifeq:{{{side|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|:|}}
{{#ifeq:{{{side|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|{{!}}|{{!}}-}}}}
|{{#ifeq:{{{nobreak|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes||<div style="text-align:{{{align|left}}};">}}{{

At around line 71 there is a closing </div> tag that is used regardless of the result of the conditional statement. Doesn't the conditional statement need to have an opening tag for each result to avoid cases that place a closing tag without an opening tag? It seems that the last bit of the conditional statement should be changed from:

|{{#ifeq:{{{nobreak|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes||<div style="text-align:{{{align|left}}};">}}{{

to:

|{{#ifeq:{{{nobreak|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|<div>|<div style="text-align:{{{align|left}}};">}}{{

--PerkinsTaylor (talk) 23:51, 8 September 2010 (UTC)

Columns?

Is it possible to get a TOC to display in two or more columns? Mjroots (talk) 05:14, 16 September 2010 (UTC)

I need a new TOC . . .

Hello, all. I hope you are doing just fine today. Anyway, what I need is a (I think) horizontal TOC to go across the top of List of California public officials charged with crimes. Can anybody help? Sincerely, GeorgeLouis (talk) 17:14, 28 May 2011 (UTC)

Move?

The following discussion is an archived discussion of the proposal. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

Page moved. Sorry about the double template, but I did not realize how the new interface would deal with a template move. Since there are a ton of links, I'll let the bots fix the redirects unless someone wants to fix those now. Also while this form of the name is not normal, I went with it since there were no objections in the discussion. I'll create the requested redirect. Vegaswikian (talk) 07:58, 9 March 2012 (UTC)

Template:CompactTOC8 → Template:CompactTOC – Obviously, this is the only "CompactTOC" template that exists at this time. If "CompactTOC" doesn't work, why not Template:Alphabetical TOC? --George Ho (talk) 02:30, 2 March 2012 (UTC)

• Hell yes! This was my goal and when I created this in 2007, and was actually what TfD decided was the right thing to do, I just couldn't do it because I wasn't an admin [the template editor bit did not exist at that time], and no one else got around to it until now. I'd suggest Template:Compact ToC for clarity, but redir from CompactTOC. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 00:24, 3 March 2012 (UTC)

The above discussion is preserved as an archive of the proposal. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

Template modified?

Has this template been modified to be a strict width? Because now I'm seeing lots of longer headers in the TOC being broken onto two lines, like "Features and abilities" here. Darkwarriorblake (talk) 14:35, 10 August 2012 (UTC)

not sure what you are talking about. that article doesn't use template:Compact ToC. Frietjes (talk) 19:38, 10 August 2012 (UTC)

Oh, for some reason Template:TOC redirects here. Darkwarriorblake (talk) 19:47, 10 August 2012 (UTC)

the table of contents is generated by a different process. you can see which templates are used on an article by opening up the article in edit mode, and reading the list of transcluded templates at the bottom of browser page. Frietjes (talk) 20:08, 10 August 2012 (UTC)

I have also noticed this problem, the text wraps longer section headings when using Google Chrome but not with Firefox. If this template is not being used to generate the default TOCs then the problem should be highlighted to the right people (Village pump?). Nimbus (Cumulus nimbus floats by) 22:56, 29 August 2012 (UTC)

hlistification

Hey folks,

I've spent a while reimplementing this as a proper horizontal list. The output has slightly changed, but the code is much cleaner and the end result is closer to that of other TOCs (including the addition of working collapsibility). Code is in the sandbox: comparisons are in the test cases. There's one remaining bug in that the lists are no longer centered when the template is, but this is a minor detail and I don't think it'll be missed (unless someone can fix it). Other than that, there's a change in that the template gains bullets: if people violently disagree with that, we can get the site CSS updated to hide them. Thoughts? If there's no opposition to this I'll roll it out in a few days. Chris Cunningham (user:thumperward) (talk) 13:19, 12 February 2013 (UTC)

it looks like the problem is with hlist + toc,

without class

1 2 3

there is also a problem with wikitable

class = wikitable

1 2 3

I believe this has been discussed at MediaWiki talk:Common.css. Frietjes (talk) 18:22, 12 February 2013 (UTC)

I found the thread. the work around for wikitable is as follows

class = wikitable hlist

1 2 3

but it still doesn't work for toc

Frietjes (talk) 19:21, 12 February 2013 (UTC)

New code drop

I've now deployed the hlistified code from the section above. This gives us a significantly cleaner and more elegant codebase along with a more semantically meaningful output and a collapse button like regular TOCs. There are a couple of caveats:

1. This introduces bullets between the elements. They're provided for free by the list styling, rather than being hacks as in some previous custom TOCs, but this is still a slight departure from the old layout. If there's consensus to remove these we can do it using the site's CSS; there should be no need to change the code here.
2. The lists are no longer centered in certain cases, per the section above. This has already been flagged as a skin issue and is awaiting a fix.

Chris Cunningham (user:thumperward) (talk) 15:50, 22 February 2013 (UTC)

no fix will be made to MediaWiki:common.css to fix the centering issue if no one else actually comments in the thread. the note will simply be archived with no changes if no one else says something. Frietjes (talk) 15:59, 23 February 2013 (UTC)

I'll try to ensure it's followed up. I would imagine that if it causes anyone any particular distress that we'll hear about it soon enough anyway, given that the code is now live. Chris Cunningham (user:thumperward) (talk) 10:30, 25 February 2013 (UTC)

The results I'm seeing when I look at Template:Compact ToC/doc's examples are all just fine.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  05:57, 7 September 2014 (UTC)

@Thumperward and SMcCandlish: so we should remove the |align= since it's broken and no one cares that it doesn't work? Frietjes (talk) 16:38, 7 September 2014 (UTC)

The cases I'm seeing under #hlistification seem bad; I'm just saying that the examples in the /doc page seem fine, so I'm unclear on what the problem is and whether it's still extant.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  20:18, 7 September 2014 (UTC)

I'm quite certain that we do want it centered, almost always. If we can't have control and have to hard-code something, it would be better to not be able to force it to the left than to not be able to center it.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  02:06, 8 September 2014 (UTC)

@SMcCandlish: yes, centering by default would be a good idea. the problem is that we don't even have the option of centering the list. as stated above, changes will be needed in MediaWiki:common.css fix the problem, but no one else commented in the thread I started. If you think it's important, perhaps you can start a new thread there? I'm sure Edokter could fix it. Frietjes (talk) 14:46, 8 September 2014 (UTC)

Added a fix. Lets see how it works. -- [[User:Edokter]] {{talk}} 16:03, 8 September 2014 (UTC)

Edokter, unless someone rewrites this template to use tables instead of divs, it doesn't work. Frietjes (talk) 16:09, 8 September 2014 (UTC)

Ooh... it's not a table? I was going for the example above. Which element would need fixing then? -- [[User:Edokter]] {{talk}} 16:12, 8 September 2014 (UTC)

Edokter this fixed it for me, but there may be a better solution. Frietjes (talk) 23:16, 8 September 2014 (UTC)

Edokter, so, it can't be fixed this way? if that's the case, I will remove |align= from the template, and update the documentation. Frietjes (talk) 21:43, 12 September 2014 (UTC)

No, you're on the right track, but I would like to include table-based TOCs as well. -- [[User:Edokter]] {{talk}} 22:16, 12 September 2014 (UTC)

Edokter, since it seems like this will never be done, I will add a note to the documentation. Frietjes (talk) 15:06, 27 September 2014 (UTC)

Frietjes, it can be done... if I knew what the goal is. The above samples are not representative; I need to know which templates are involved and what the desired default behaviour is. -- [[User:Edokter]] {{talk}} 17:15, 27 September 2014 (UTC)

Edokter Search for 'align=center' in the testcases. The text should be center-aligned in those cases. Thanks! Plastikspork _―Œ^(talk) 01:39, 28 September 2014 (UTC)

That seems simple enough; all that is needed is

.toc.hlist ul,
#toc.hlist ul {
    text-align: inherit;
}

That will take care of this template anyway. -- [[User:Edokter]] {{talk}} 07:40, 28 September 2014 (UTC)

Parameters for _TOC_

Where is a list of parameters for _TOC_? I want a vertical TOC, not a compact (horizontal) one. Template:TOC redirected me here, to Template:Compact_ToC. Thank you. {{u|Checkingfax}} ( Talk ) 19:36, 17 October 2015 (UTC)

TOC itself does not have any parameters. See H:TOC and Category:Wikipedia table of contents templates for a list of templates. -- [[User:Edokter]] {{talk}} 08:41, 18 October 2015 (UTC)

Feature request: non-Latin character set

I have a need on an independent MediaWiki for a Compact ToC that displays both Latin and Hiragana characters at the same time. Is this possible? --Rob Kelk 13:27, 21 August 2016 (UTC)

yes. Frietjes (talk) 13:32, 18 September 2016 (UTC)

Requested move 21 January 2017

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: no consensus. Proposed title created as a redirect. Jenks24 (talk) 07:39, 19 February 2017 (UTC)

---

Template:Compact ToC → Template:Compact alphabetic ToC – Current name is too generic. Pppery 19:08, 21 January 2017 (UTC) --Relisting. JudgeRM (talk to me) 20:18, 28 January 2017 (UTC) --Relisting. BrownHairedGirl (talk) • (contribs) 19:27, 9 February 2017 (UTC)

• Oppose. I see no real clear need to rename this, considering that it's a template. However, I'm not opposed to creating the proposed title as a redirect to this page. Steel1943 (talk) 21:42, 17 February 2017 (UTC)
• Support per WP:PRECISION. Laurdecl ^talk 02:15, 18 February 2017 (UTC)
  • WP:PRECISION usually doesn't (and, in my opinion, shouldn't) apply to template titles. Otherwise, titles like Template:Tl, Template:Tlx, Template:RA and even Template:Information would have to be moved as well. Steel1943 (talk) 04:52, 18 February 2017 (UTC)
    • I'm not seeing any exception for templates in the policy page. I also don't see why those other templates would have to be moved. The fact remains that this is not a Compact ToC. It is a Compact alphabetical ToC. Laurdecl ^talk 02:27, 19 February 2017 (UTC)
      • WP:PRECISION redirects to a section on the page titled Wikipedia:Article titles. Steel1943 (talk) 03:54, 19 February 2017 (UTC)
• Oppose - I see good intentions to be precise, but typing {{compact alphabetic ToC}} is... not something I would type. As Steel1943 said, it can be created as a redirect, but that's all. Of course, if the current title proven too ambiguous, like {{plot}}, which became {{long plot}}, we can revisit this later. --George Ho (talk) 04:30, 19 February 2017 (UTC)

---

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

Thread notification: suggestion for simplified horizontal toc

https://en.wikipedia.org/wiki/Template_talk:Horizontal_TOC#Suggest_version_of_Horizontal_TOC_that_doesn't_display_section_numbers.

GregKaye 13:24, 13 September 2017 (UTC)

Stripped tags

In revision of 15:45, 22 February 2013 by User:Thumperward of {{Compact ToC}}, 2 stripped </ul> tags were introduced. I believe this is an error. —Anomalocaris (talk) 09:21, 6 November 2017 (UTC)

Wasn't sure what you meant at first. In looking over the code, I don't find corresponding <ul> opening tags, so I think that's what you're reporting. That does seem to be an error, unless there's somewhere else that missing markup would be injected from and we're certain that it will happen for any case in which the </ul> code is in the output. That seems unlikely.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  11:43, 6 November 2017 (UTC)

I replaced the orphaned </ul> with newlines to break the lists. as far as I can tell, this produces the same output, but without requiring HTML tidy to fix it. Frietjes (talk) 14:26, 6 November 2017 (UTC)

Oh, okay. I was monkeying with it in the sandbox, but you've beat me to it.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  16:34, 6 November 2017 (UTC)

Non-breaking space following "Contents"

There's a non-breaking space after the word "Contents" but before the colon, but if the |name= parameter is specified, this space is omitted. Can we just remove it (in other words, change "Contents :" to "Contents:")? – voidxor 04:40, 14 July 2017 (UTC)

@SMcCandlish and Frietjes: You both seem to know this template's code like the back of your hand. Any thoughts on removing the errant space described above? – voidxor 01:05, 12 November 2017 (UTC)

Too tired to look into it right now; I put an {{edit template-protected}} on it it to attract others' attention (and am actually going to go have this put under that protection level, because it's easily vandalized and could mess up a lot of articles).  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  09:54, 12 November 2017 (UTC)

Another issue is that near a   (maybe the one under discussion above, maybe not), there's a call to {{MediaWiki:Toc}}, but that page no longer exists. I'm don't recall what the purpose of that was, but I wonder if the issue above has something to do with this. That code post-dates my work on this template, I think.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  09:59, 12 November 2017 (UTC)

@Voidxor and SMcCandlish: I removed the nbsp before the colon. {{MediaWiki:Toc}} no longer exists because it is a "system message" filled in by the mediawiki backend software (see here). Frietjes (talk) 13:42, 12 November 2017 (UTC)

@Voidxor, SMcCandlish, and Frietjes: The non-breaking space before the column colon was indeed wrong typography, however a space was missing after the column colon; I have now added it. See usage example on List of one-word stage names (nominated for deletion, that's where this typographical issue got my attention). — JFG ^talk 12:11, 18 March 2018 (UTC)

@JFG: Do you mean "colon"? If so, I agree. I too noticed that missing space (even though that wasn't my original concern), and it looks much better now, thanks. – voidxor 19:49, 18 March 2018 (UTC)

Haha, good catch. Ever read my column about Colón? — JFG ^talk 03:33, 19 March 2018 (UTC)

Yes, clearly the space was intended to be there, it was just put on the wrong side of the colon.  — SMcCandlish ☏ ¢ 😼  20:54, 22 March 2018 (UTC)

Insert break

Is there away to insert a break in the contents? I am having trouble with the template at List of feminist comic books, where the template forces the boxes on the left to clear under it on mobile devices and other narrow resolution displays. Breaking the contents into two rows may help.--TriiipleThreat (talk) 14:59, 30 March 2018 (UTC)

Inserting additional items in middle

I'm editing the page List of Egyptian hieroglyphs which uses this template. The hieroglyphs are sorted into sections on letters A-Z and Aa, NL and NU. Would there be any way to insert NL and NU after N? Thanks! Trialpears (talk) 16:46, 11 May 2019 (UTC)

Template-protected edit request on 30 August 2020

Please improve template formatting as to avoiding the rendering of excess blank lines beneath transclusions, like here, for instance.--Hildeoc (talk) 13:49, 30 August 2020 (UTC) Hildeoc (talk) 13:49, 30 August 2020 (UTC)

 Not done if you have a specific change, please make it in the sandbox and test, then reactivate the request. To just continue discussing this improvement - please continue below! — xaosflux ^Talk 15:46, 30 August 2020 (UTC)

Edit request

Please add the template TOC hidden, perhaps to the 'see also' section. Thank you - wolf 04:18, 3 August 2021 (UTC)

To editor ­wolf:  Not done: {{edit template-protected}} is usually not required for edits to the documentation or categories of templates using a documentation subpage. Use the 'edit' link at the top of the green "Template documentation" box to edit the documentation subpage. And thank you for your input! P.I. Ellsworth  ed. ^put'r there 13:07, 3 August 2021 (UTC)

I see now. (I don't edit template pages).  Done now (and thanks, for the whole "teach a man to fish", yadda, yadda, yadda bit.) Thanks & Cheers - wolf 13:26, 3 August 2021 (UTC)

It's my pleasure! Paine  14:28, 3 August 2021‎ (UTC)

meaningless code

{{#if:{{{a}}}}} is always true. Isn't it {{#if:{{{a|}}}}}? --Naggy Nagumo (talk) 03:20, 18 January 2021 (UTC)

Naggy Nagumo, consider {{Compact TOC|a=}} to suppress the link to A (per the documentation). Frietjes (talk) 15:08, 3 August 2021 (UTC)

Class noprint

I thought that class=noprint would exclude this from the print version, but it doesn't seem to be working on my browser? Thanks! Plastikspork _―Œ^(talk) 22:52, 31 August 2021 (UTC)

Plastikspork, if you put the class in the outer div, it works (see the sandbox). Frietjes (talk) 18:47, 1 September 2021 (UTC)

now implemented. Frietjes (talk) 21:05, 8 September 2021 (UTC)