Template talk:Cast listing/Archive 1
| This is an archive of past discussions about Template:Cast listing. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
| Archive 1 |
White space
What's up with all the white space this template is now generating since it was moved to the current (awkward) title? Is there any way to fix this? Ribbet32 (talk) 00:05, 29 October 2018 (UTC)
- Fixed, I believe. —Joeyconnick (talk) 06:07, 29 October 2018 (UTC)
Please change this template to "Cast list"
Why is this template not "Cast list"? Can we try to avoid adding deliberate misspellings to the markup? There are too many genuine spelling mistakes in Wikipedia and deliberately adding more in the markup means editors are less likely to notice the actual spelling and bother to fix them. This might not seem like a problem but sooner or later like MOS:BOLD and WP:OVERLINK it will need to change, so please fix this relatively new template before it becomes more widely use.
Ideally if you could change the template to "Cast list" and leave "Castlist" as a redirect, and also set the template up so that in Preview mode editors get a warning to preferably use the correctly spelled version. -- 109.76.255.192 (talk) 14:32, 20 July 2018 (UTC)
- I see that "Cast list" does also work so I suppose that makes this a Page move request. -- 109.76.255.192 (talk) 14:34, 20 July 2018 (UTC)
- Someone changed it to "Cast listing" which is consistent with Template:Track listing. -- 109.76.134.87 (talk) 18:17, 13 May 2019 (UTC)
Why fixed colwidth?
@Debresser: could you please point me to the discussion where the current consensus of a fixed colwidth of 25em was established? --bender235 (talk) 23:04, 7 June 2020 (UTC)
- Please see the first line of this template's documentation. Debresser (talk) 23:41, 7 June 2020 (UTC)
- Thanks.
And how exactly is a {{cast listing}} template with a hard-coded colwidth allowing for the apparently agreed upon exception that says "unless there is a compelling reason to use a different value"?Oh, I see. The general recommendation was to use {{div col}}. --bender235 (talk) 00:05, 8 June 2020 (UTC)
- Thanks.
Font size
On a mobile device (Edge browser on Android phone the text renders at reduced font size. Is that deliberate? GraemeLeggett (talk) 19:14, 30 July 2020 (UTC)
Alternate
Template {{Castlist}} works as well (Cast listing or Castlist).Eschoryii (talk) 23:00, 7 January 2021 (UTC)
- That is called a "redirect, meaning that Template:Castlist redirects to Template:Cast listing. Debresser (talk) 13:35, 8 January 2021 (UTC)
I saw a case of an editor changing from {{Cast listing}} to {{Cast list}} claiming in the edit summary that this somehow had an effect on how the page worked for mobile viewers? "(→Cast: So it works on all mobile devices)
"
Is there a difference? If so why? (If there isn't then why an editor claim there was?) Seems very strange. -- 109.76.203.103 (talk) 14:39, 5 February 2021 (UTC)
- I see from above that things render different on mobile devices, but does using one name over another really make any difference to the rendering? -- 109.76.203.103 (talk) 14:42, 5 February 2021 (UTC)
What is the use of unnamed param 2?
I don't see any use for it as it just fallbacks to param 1 in case it's not set and will override 1 if set. — DaxServer (talk to me) 09:25, 16 October 2021 (UTC)
- Where are you seeing this param? I checked the Template page and didn't see a second param. Thanks for clarifying! DonIago (talk) 16:58, 16 October 2021 (UTC)
<includeonly>{{#if:{{{2|{{{1|}}}}}}|{{div col | colwidth = 25em | gap = {{{gap|}}} | rules = {{{rules|}}} | small = {{{small|}}} | style = min-width: min(25em, 100%); {{{style|}}} | content = {{{2|{{{1|}}}}}} }} }}</includeonly><noinclude>{{documentation}}</noinclude>- Isn't this what you see, with a
{{{2|in the#ifandcontent? (excluding the colons at the beginning, not sure how to format the code block) — DaxServer (talk) 17:18, 16 October 2021 (UTC)- Ah, thanks. Unfortunately I can't really speak to that. Perhaps it's "legacy" code that could be removed to simply the template? But it may have also been added to solve problems. This may be a case of WP:NOTBROKEN. But, in any case, sorry, I have no idea what that does. DonIago (talk) 23:27, 16 October 2021 (UTC)
- It looks like it's always been there and effectively is legacy code from the original template I 'borrowed' to create this one originally. If someone familiar with coding wants to make the changes to clean that up, I have no objection. DonIago (talk) 23:32, 16 October 2021 (UTC)
- I see, thanks for the lookup ;) I've added TemplateData in the documentation and will show up in a few hours. I've deprecated the 2, I'll later verify the usages of the template to confirm it's not used and then remove the param. — DaxServer (talk) 08:15, 17 October 2021 (UTC)