![]() | This is an archive of past discussions. 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 | ← | Archive 5 | Archive 6 | Archive 7 |
Please take a look at the sandbox and testcases. I've updated the code with the following changes:
|TranslitTitle=
, |NativeTitle=
and |NativeTitleLangCode=
. This should enable us to remove {{
Japanese episode list}} per the merge result and correctly handle non-English languages, as the module now uses
Module:Lang for these languages.|NumParts=
and |Title_n=
parameters. This should enable us to remove {{
Japanese episode list multi-part}}.|NumParts=
and |Serial=
.|EpisodeNumber=
was not used.There should be no bugs still in the code, but test it out and let me know if you have any comments. -- Gonnym ( talk) 17:41, 16 January 2019 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
As requested above, would appreciate if any template editor can verify my code on Module:Episode list/sandbox throws no errors. -- Gonnym ( talk) 07:16, 28 January 2019 (UTC)
In "Double episodes", the Live template shows "22, 24" and the Sandbox shows "22–24", which has a different meaning (i.e. 22, 23, and 24). Is this change intentional? Other than these two minor problems, the rest of the test cases look perfect to me. – Jonesey95 ( talk) 15:59, 30 January 2019 (UTC)
Any other comments? Did anyone see any errors in the code on main-space pages? -- Gonnym ( talk) 12:12, 3 February 2019 (UTC)
|1=
- For TemplateData there is no such thing as an unnamed parameter and it treats all unnamed parameters as numbered parameters. So |1=
is necessary for the documentation. Since
Template:Episode list/sublist was setup to use this documentation page, and that template needs it, not a lot I can do here. However, as I've noted
here, if the usage of this parameter is only used in one of these templates and not both, I can eliminate the need for it altogether and get that data without user input.|1=
.|1=
and unnamed is the same thing - it's not a change in the code or something (accessing an unnamed parameter in lua is accessing it from the numbered/position its placed). Not really sure what change you want me to make in the documentation.The WMF asserts that its policies "may not be circumvented, eroded, or ignored by Wikimedia Foundation officers or staff nor local policies of any Wikimedia project- are you sure you want to get into this? (regarding your question about the incorrectly placed values, the next sentence I wrote has that answer - you're adding a story arc title AND episode title in the same field - that is mashing two distinct fields into one) -- Gonnym ( talk) 17:15, 4 February 2019 (UTC)
|1=
used in tables that aren't transcluded? It isn't, and thus shouldn't be used in the documentation. And I'm aware that it's the same thing, but they are used differently. I've never seen {{
Episode list/sublist|(newline)1=Article}}
, only ever {{
Episode list/sublist|Article}}
.|1=
or you can use it without it - it is the same thing when invoking a template. The documentation still needs to call it "1" as you can't call an unnamed parameter unnamed. This is a rather pointless argument. Also, I find it amazing that a veteran editor like yourself knowingly ignores accessibility issues and the actual point in that policy which states that I actually do not need a consenous to point out that your usage in the Doctor Who articles is incorrect. Pretty amazing Alex. --
Gonnym (
talk)
00:55, 5 February 2019 (UTC)
|1=
. But I agree, it is pointless, so I'll update the documentation accordingly. And truly, I live to amaze; if you want to change the articles from their standing layouts, I'll be there to restore and wait for a discussion. Cheers. -- /
Alex/
21
01:04, 5 February 2019 (UTC)
The onus is on you if you want to create a consensus to change that, and if another editor implements improvements to eliminate theAvoid using
<br>
tags in adjacent cells to emulate a visual row that isn't reflected in the HTML table structure. This is a problem for users of screen readers which read tables cell by cell, HTML row by HTML row, not visual row by visual row.
<br>
tags, any reversion will certainly be viewed as
disruptive editing. Is that clear enough for you? --
RexxS (
talk)
16:47, 5 February 2019 (UTC)
<hr>
. Same layout given, no <br>
tag, no issues in DTAB with <hr>
, and quite fitting as this module already uses <hr>
to split rows. -- /
Alex/
21
22:35, 5 February 2019 (UTC)
<hr>
used either, then state a policy that bans it and/or remove it from this module as well. -- /
Alex/
21
23:33, 5 February 2019 (UTC)
<hr>
or <div>...</div>
or <p>...</p>
or any other block-level html to put text on new lines within a table cell produces exactly the same problem for a screen reader user. --
RexxS (
talk)
00:02, 6 February 2019 (UTC)
"website developer in my spare time". Any web developer worth their salt understands accessibility issues; you can start at WCAG. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:10, 6 February 2019 (UTC)
Directed here from
Wikipedia talk:WikiProject Doctor Who#Season articles layout change. Clear improvement to align with site-wide consensus at
WP:DTAB, which the Doctor Who project is currently violating. Pleased to learn that <br>
should not be used going forward for the benefit of those using screen readers. No objections at all to the proposed changes.
U-Mos (
talk)
03:20, 7 February 2019 (UTC)
On another interesting note, why the separate rows for identical directors and writers, but a rowspan for the title? An Unearthly Child applies to the whole serial, as does the director and writer, Waris Hussein and Anthony Coburn. Same for the production code. -- / Alex/ 21 03:52, 7 February 2019 (UTC)
<hr>
tag is acceptable for the multi-title example, then that means that the Doctor Who articles can indeed use the <hr>
tag instead of <br>
. [T]here should be no problem that I can foresee.-- / Alex/ 21 08:41, 7 February 2019 (UTC)
[a]s long as whoever uses that technique understands that a screen reader will effectively ignore the horizontal rule and will read out the entire contents of that table cell as if the rule wasn't there, then there should be no problem that I can foresee.No comment was made in that thread discerning the use of
<hr>
in only a singular column vs. multiple columns. If it can be used in one column, why can it not be used in multiple columns? Or, on the other hand, if it cannot be used in multiple columns, why can it be used in one column? -- /
Alex/
21
09:05, 7 February 2019 (UTC)
Title |
---|
Galaxy 4 |
Four Hundred Dawns |
Trap of Steel |
The Exploding Planet |
Air Lock |
Title |
---|
Galaxy 4 Four Hundred Dawns Trap of Steel The Exploding Planet Air Lock |
Title | Air date |
---|---|
Galaxy 4 | |
Four Hundred Dawns | 11 September 1965 |
Trap of Steel | 18 September 1965 |
The Exploding Planet | 25 September 1965 |
Air Lock | 2 October 1965 |
Title | Air date |
---|---|
Galaxy 4 Four Hundred Dawns Trap of Steel The Exploding Planet Air Lock |
11 September 1965 18 September 1965 25 September 1965 2 October 1965 |
How do the updates solve the accessibility problems of using block elements like those seen at Agents of S.H.I.E.L.D. (season 2)#ep43, List of Unbreakable Kimmy Schmidt episodes#ep48, Big Mouth (TV series)#ep21 and/or Once Upon a Time (season 4)#ep74? -- / Alex/ 21 11:54, 20 February 2019 (UTC)
|DifferentDirectors=
and |DifferentWriters=
parameters, which when set to true, will check for DirectedBy_# and WrittenBy_# parameters. Does this work for what you need? --
Gonnym (
talk)
08:33, 24 February 2019 (UTC)
|Serial=
. If there are other styles that work differently, then if needed I'll change the code to this setup. Let me know what's needed, and if I need to change something or add the sandboxed code. --
Gonnym (
talk)
09:12, 24 February 2019 (UTC)
|WrittenBy_1=
, |WrittenBy_2=
and |WrittenBy_3=
but only |DirectedBy_1=
and |DirectedBy_2=
, there is no way to know what the editor meant by that and the system shouldn't be used for guessing. So in this case |NumParts=
should still be used and all para# parameters should have the matching number of entries. Other than that I think it could work. Will have time later to work on it. --
Gonnym (
talk)
10:26, 24 February 2019 (UTC)
|DirectedBy_3=
with {{
TableTBA}}, as empty cells currently and already are, and add the article to a tracking category. I'll see if I can implement some sandbox changes and whip up some test cases. -- /
Alex/
21
10:29, 24 February 2019 (UTC)|Serial=
and |NumParts=
; the less parameters to deal with, the better. -- /
Alex/
21
11:38, 24 February 2019 (UTC)
|NumPart=
parameter, as you are looping over 100 entries for each column, while the values could be 2 or 3. Rest of the code seems good. --
Gonnym (
talk)
12:13, 24 February 2019 (UTC)
|NumParts=
; guess it is better to keep that. Still working out the multiple titles issue, not sure why that's erroring. -- /
Alex/
21
23:23, 24 February 2019 (UTC)Dear Admins,
The short summary is not appearing on my page no matter what? Kindly help me figure out what i am doing wrong? Page is Draft:The Fish'n Canada Show Thank You! -- KoolKrazy ( Talk To Me!)
Gonnym, I had to revert the most recent change because it added several articles to Category:Pages with script errors including List of Good Mythical Morning episodes, List of Horizon episodes, The Dr. Oz Show, and List of The Nature of Things episodes. I imagine it's due to the string processing on very large input. perhaps if these pages are fixed, we can add the tracking back again? Frietjes ( talk) 22:02, 25 October 2019 (UTC)
Per the ongoing discussion at
TfD there is some desire to add |Guests=
and |MusicalGuests=
as an alternative to using the less obvious |Aux1=
and |Aux2=
in the ca. 106 pages using {{lnep}}
. are there any objections to adding these parameters?
Frietjes (
talk)
18:16, 6 December 2019 (UTC)
How is the id parameter set on a table row created with Episode list to create a row anchor for a sectionlink, see Help:Table#Section link or map link to a row anchor? Jim Craigie ( talk) 17:24, 28 November 2019 (UTC)
row:tag('th')
:attr('scope', 'row')
:attr('rowspan', numberOfParameterGroups)
:attr('id', 'ep' .. idTrim(idTrim(episodeNumber, ' ----'), '<'))
:css('text-align', 'center')
:wikitext(episodeText)
row:tag('td')
:attr('id', 'pc' .. idTrim(idTrim(args.ProdCode, ' ----'), '<'))
:css('text-align', 'center')
:wikitext(args.ProdCode)
|EpisodeNumber=
uses <hr />
or <br />
(or any other HTML tag), then the anchor is the first number. If the |EpisodeNumber=
uses –
(or anything else), then the anchor is whatever is displayed/used.1<hr>2
is #ep1
, the anchor to 1–2
is #ep1–2
, and the anchor to 1–2
(as the example article previously used) would literally be #ep1–2
(see
Special:Permalink/927849664#ep1–2 ). -- /
Alex/
21
23:57, 28 November 2019 (UTC)
#ep1–2
does not work – it actually has to be #ep1&ndash;2
not just for display, but to make the link work.
Jim Craigie (
talk)
05:48, 29 November 2019 (UTC)
If you are updating Episode list would it be possible to create a third ID containing the |Title=
parameter value – it would be much easier to use than having to find the episode number (and its format, which may change invalidating links – if anyone had previously created links into Silent Witness episodes using
Alex's solution then
IJBall's edit tonight has just invalidated them all!), and production numbers don't exist publicly for UK productions?
Jim Craigie (
talk)
06:30, 29 November 2019 (UTC)
@ Alex 21:, while we are fixing issues with the episode ID, do you have any idea for a solution for cases where we have a specials or webisode table? List of Heroes episodes as an example. Can't like to any specific episode, is they share the anchor with regular episode. -- Gonnym ( talk) 08:28, 29 November 2019 (UTC)
{{
Episode table}} now supports |anchor=
which allows duplicate numbering on the same page. See doc for more info. --
Gonnym (
talk)
06:25, 13 January 2020 (UTC)
Where is the raw code for this template so that some people have the ability to use it on other mediawiki sites? — Preceding unsigned comment added by 69.137.181.135 ( talk) 17:48, 14 January 2020 (UTC)
Has any thought ever been given to adding an optional parameter for episode lengths? With an increasing number of shows where this varies, seems it would be useful information to tabulate in some cases. U-Mos ( talk) 21:20, 7 February 2020 (UTC)
Is there anything that can be done about the way this template displays on mobile? Someone posted this screenshot on Reddit: instead of wrapping the text, it merely cuts it off and nothing can be done to scroll over and view it. Adding a scrollbar would be just as ugly, but can't the table width be set to fit the window and automatically wrap? Thanks. —Мандичка YO 😜 16:21, 9 March 2020 (UTC)
nothing can be done to scroll over and view it. Additionally, I don't really think there's anything that can be done because the table inherently is larger in px width than your standard mobile phone display. - Favre1fan93 ( talk) 17:02, 9 March 2020 (UTC)
I don't think the template should automatically fill in "TBA" and "TBD" for empty values. That sort of assertion is not encyclopedic. The template should only list information that's available without guesswork about something that "will be announced" or "will be determined." Some episodes are many decades old and the missing information will never be announced or determined. Even with new shows, it's presumptuous that some missing information will be announced or determined. NameMyRemember ( talk) 09:17, 24 March 2020 (UTC)
The template has no parameter for 'Duration' or 'Total length'. I think it should be, as it's useful for many users like me. Thank you. Empire AS Talk! 08:27, 31 July 2020 (UTC)
Seems to be broken right now. 2601:14F:4500:4300:E56D:E54A:DAA7:549B ( talk) 07:50, 4 August 2020 (UTC)
Without | EpisodeNumber field, title becomes bold. See for example List_of_Sailor_Moon_episodes#Shorts. Smeagol 17 ( talk) 11:12, 3 September 2020 (UTC)
Hello maintainers 👋
While editing Elmo's World, I noticed that the background to references added for accessibility looks different on Chrome than they did in Firefox. The result does not look good and is not accessible as roughly half of the reference does not have a high contrast.
I took a crack at modifying the inline CSS and was able to get it to look good in Chrome but but it subsequently broke it in Firefox.
Some things we could consider to fix this is:
I'd be happy to work on this, but I'd appreciate some input first. — motevets ( talk) 15:51, 15 September 2020 (UTC)
I think the TBA default entry should be removed or replaced by a dash. It shows up in episode lists of old shows where the director and/or writer are unknown or information hasn't yet been entered into the article. That is clearly not the same thing as "to be announced". 93.136.110.156 ( talk) 06:40, 4 December 2020 (UTC)
{{
TableTBA|N/A}}
. -- /
Alex/
21
02:05, 10 December 2020 (UTC)It would be great if the module could get data like title, director, screenwriter, etc. from Wikidata if not specified in the article. For example on The No. 1 Ladies' Detective Agency (TV series)#TV series (2009) I could write
{{Episode list|qid=Q102864920}}
and all relevant data would be read from Wikidata. Apart from the summary (which would need to remain in the article) most of the other fields are supported in Wikidata — Martin ( MSGJ · talk) 20:05, 4 December 2020 (UTC)
Not sure if this has been discussed before, but is there a reason why there is no EpisodeNumber_1, EpisodeNumber_2, EpisodeNumber2_1, EpisodeNumber2_2, etc.? - adamstom97 ( talk) 08:08, 9 December 2020 (UTC)
<hr>
to separate episode numbers (as the only usage for that tag is a "visual" separation), we can just use dashes for episode numbers, as it shows the spanning range. -- /
Alex/
21
02:08, 10 December 2020 (UTC)
<hr>
). -
adamstom97 (
talk)
07:03, 10 December 2020 (UTC)Despite having a mobile website (that still looks completely different to the desktop website) for some years now, this template hasn't been updated to work well on phones. Sticking prose into a table that requires constant side-to-side scrolling on narrow screens isn't a great idea. List of Not Going Out episodes is a particularly awful example of this. Why is the Wikipeedia "community" so consistently uncaring about half your readership? Perhaps one of the 'template editors' could do some template editing to bring this template into the 2010s (a decade late). Oh, DrPizza! ( talk) 02:57, 11 January 2021 (UTC)
uncaringabout being polite to your fellow editors and template editors? -- / Alex/ 21 04:37, 11 January 2021 (UTC)
ShortSummary
parameter. This causes the text to wrap to the width of the table, which on phones is often wider than the width of the screen. So a solution would seem to be to remove the non-tabular data from being inside a table. Let tables be used for the tasks they were designed for instead of doing double duty as a (poorly-working for half your readership) container for a paragraph or two of text.Yawn.Are you bored? That would be a shame. I thought you enjoyed being a pugnacious wikisoldier. Well, participating in this discussion is entirely optional. Oh, DrPizza! ( talk) 03:58, 17 January 2021 (UTC)
As for the issue of side-to-side scrolling, there is no way to resolve this other than to remove the summaries altogether.As stated, the prose summaries should be taken out of a table and put into compliance with your own MOS. Something like this. The separate episode "rows" can still be combined into a consolidated table:
Something like this.God, that's horrifying and a complete violation of tabular formatting and accessibility policies. Absolutely not. Thanks for the suggestion but let's take a heavy pass. I can guarantee you're going to get 0% consensus from any WikiProject for that. I mean, you're welcome to try, though. Go for it. -- / Alex/ 21 04:02, 17 January 2021 (UTC)
I have a question regarding the first example under Template:Episode list#Non-English titles. Following WP:ROMAJI, I was expecting it to be written "Pokémon", because that is the common English name, based on the title and text of the article Pokémon. Custardbandlers says following WP:ROMAJI it should be "Pokemon" because that's the Hepburn romanization. Which is correct? Thanks! -- Beland ( talk) 04:28, 5 March 2021 (UTC)
There's no explanation of what Episode list/sublist is for in the documentation. There are usage examples but no clear description of it's purpose. What is the purpose of sublist? - X201 ( talk) 07:49, 23 April 2021 (UTC)
The episode table at Seabound_(Ninjago_season)#Episodes is behaving strangely, and I can't figure out why. The Viewers parameters are empty, and the template adds "N/A" to the Viewers column for episodes 1 thru 6, but adds "TBD" to episodes 7 thru 16. Any ideas?— TAnthony Talk 16:18, 19 May 2021 (UTC)
|Viewers={{TableTBA|TBD}}
. -- /
Alex/
21
21:20, 19 May 2021 (UTC)Episode guides are still painful to read on mobile because the episode metadata columns are too wide, forcing the description field to be wider than the screen, such that you have to scroll horizontally back and forth to read them. This screenshot from a tweet 6+ years ago shows the problem that still exists today: https://twitter.com/jelsert/status/659548147086204928
It's 2022, and the rest of the web has solved this with responsive web design a decade ago. What would it take to fix this? It would require updating the CSS, but I have no idea who is responsible for that, or how we could encourage that? -- ToastyKen ( talk) 03:46, 11 February 2022 (UTC)
Hello! Recently I was editing
Jay Leno's Garage#Compilation (2020) to make the "Number overall" display as N/A instead of TBA since they aren't considered to be part of the main series and therefore don't have a number overall. I was forced to use /
instead of "/" as in the "episode number" parameter, the "/" character is displayed as an en/em-dash (I don't know what the difference is at first glance, all I know is one is longer). Any reason why it does this? ―
Blaze Wolf
TalkBlaze Wolf#6545
18:27, 14 March 2022 (UTC)
The title of an episode might be a more natural heading for the row in table. It also provides the link to the standalone article, if it exists, so would give this link more prominence at the beginning of the row. I will try and provide some examples of how it might look. — Martin ( MSGJ · talk) 21:32, 11 May 2022 (UTC)
No. overall |
No. in series | Title | Location | Directed by | Original air date | UK viewers (millions) |
---|---|---|---|---|---|---|
13 | 1 | " The Devil of Christmas" | Alpine chalet | Graeme Harper | 27 December 2016 | 1.03 |
Title | No. in series |
Location | Director | Original air date | UK viewers (millions) |
---|---|---|---|---|---|
" The Devil of Christmas" | 1 | Alpine chalet | Graeme Harper | 27 December 2016 | 1.03 |
Related to proposal above, I think it would be clearer, more semantic and accessible if the heading cell of each episode spanned the plot summary too. Then it would be more obvious which episode the summary related to. Mock up will be posted below. — Martin ( MSGJ · talk) 12:04, 12 May 2022 (UTC)
Title | No. in series |
Location | Director | Original air date | UK viewers (millions) |
---|---|---|---|---|---|
" The Devil of Christmas" | 1 | Alpine chalet | Graeme Harper | 27 December 2016 | 1.03 |
In a film within the episode, an English family (Pemberton, Rula Lenska, Jessica Raine and George Bedford) travel to an Austrian chalet in December 1977. They are told the story of the Krampus by their guide (Shearsmith). Meanwhile, the film's director ( Derek Jacobi) provides audio commentary. |
The description for ShortSummary is that it be a plot summary. There has been, and continues to be, a trend towards including additional information as "notes" and I've seen this from new and experienced editors alike. Where do we draw the line on what's appropriate and what's not, and should the parameter description be a little more clear on what's allowed? I think it's obvious when it's trivia. For example, I recently removed a "note" that was describing a stock footage scene in The Waltons that was also used by Gilligan's Island. But there are other less obvious situations, especially when it comes to cast. We do see a lot of guest cast noted in the ShortSummary, which I think is an appropriate place to note specific cast additions. But sometimes this gets extended to information about So-and-so appears but is not credited, or So-and-so is credited but does not appear; and for a series that uses stock credits, that can get tedious for minor characters who are in the standard credits but do not appear in every episode. Am I being too rigid in trying to figure out a bright line on this? ButlerBlog ( talk) 14:30, 23 September 2022 (UTC)
Currently, if a parameter is included (such as |DirectedBy=
) with no content, "TBA" will fill the cell. However, this doesn't necessary make sense for episodes that have not filled in the parameter after its air date. In that case, it should be "N/A" or perhaps a "–". Is this possible to add in a check against whatever is placed in the "airdate" parameter, and make it be TBA for a future episode, and "N/A" or "–" for a past one? See
A Touch of Grace, a show from the 1970s with a number of unfilled in parameters, as an example where this is a problem. -
Favre1fan93 (
talk)
21:45, 18 September 2022 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
@ Alex 21: This causes Lua errors if there's no original air date set, for example at List of Makutano Junction episodes. Please revert or fix this. -- rchard2scout ( talk) 12:41, 26 September 2022 (UTC)
Because these tables can get pretty wide, I often notice that the ShortSummary text is stretched beyond the width of a mobile device screen. The result is a poor experience on mobile where you have to swipe the screen left and right to read across the lines of the paragraph.
You should consider limiting the width of the text in the ShortSummary cell to the width of the viewport on mobile. Something like a max-width
of 90vw
would make it a lot easier for mobile users to read the summaries.
DrewBino
talk (
afc0703)
01:39, 31 January 2023 (UTC)
Per consistency with other multipart episode parameters that have been added to this template, I propose we also use EpisodeNumber_1, EpisodeNumber_2, EpisodeNumber2_1, and EpisodeNumber2_2. Many episode lists currently use <hr>
to split episode numbers, which has been objected to by
User:Alex 21 for accessibility reasons (see our own
user talk discussion), so these further NumParts additions would address those concerns. The residual dashes which are still used in certain episode lists are really less clear visually – especially the cases where directors/writers are only credited in part 1 or part 2 specifically – and the dashes are inconsistent with the visual grammar of presenting all other episode numbers vertically. Discovered this idea was
previously floated two years ago by
User:Adamstom.97, and I agree this should be implemented. --
Wikipedical (
talk)
20:46, 6 December 2022 (UTC)
Hey @ Alex 21: Could you look into this? Thanks. InfiniteNexus ( talk) 16:57, 31 January 2023 (UTC)
I've had the day off, so I thought I'd give it a crack to see what I would get. Let's analyze the following results:
No. overall |
No. in season | Title | Directed by | Written by | Original air date | U.S. viewers (millions) |
---|---|---|---|---|---|---|
43 | 21 | " S.O.S." | Vincent Misiano | Jeffrey Bell | May 12, 2015 | 3.88 |
43 | 21 | " S.O.S." | Vincent Misiano | Jeffrey Bell | May 12, 2015 | 3.88 |
Billy Gierhart | Jed Whedon & Maurissa Tancharoen | |||||
43 44 | 21 22 | " S.O.S." | Vincent Misiano | Jeffrey Bell | May 12, 2015 | 3.88 |
Billy Gierhart | Jed Whedon & Maurissa Tancharoen | |||||
43 | 21 | " S.O.S." | Vincent Misiano | Jeffrey Bell | May 12, 2015 | 3.88 |
44 | 22 | Billy Gierhart | Jed Whedon & Maurissa Tancharoen | |||
However, this new fourth example then leads me to the following observation. Notice how the airdate and viewers cells are also split, despite having equal values. The reasoning for this in the past has been that, if we have a cell that's single-spanning, all cells afterwards must also be single-spanning (i.e. we cannot have a multiple-spanning cells after single-spanning cells), due to "accessibility reasons". However, I've never seen any contributing support or documentation for this, and if we were to implement these edits, then we have single-spanning episode numbers and a multiple-spanning title following. This has also never been an issue for spanning cells in {{ Series overview}} (e.g. List of Star Trek television series), so after this edit, I would suggest that we implement the merging of those equal-valued cells to be multiple-spanning rather than duplicated single-spanning cells. -- Alex_21 TALK 05:04, 7 March 2023 (UTC)
No. overall |
No. in season | Title | Associated MCU work | Original release date |
---|---|---|---|---|
1 2 | 1 2 | "Wanda Maximoff" | WandaVision | January 8, 2021 |
"Vision" | ||||
|Title_1=
, |Title_2=
, ..., are used, they don't generate a split cell, and instead just use <hr>
between the titles, meaning none of the cells above are actually spanning, they're just all, by default, spanning one row. They're visually split, yes, which is where and why all the accessibility discussions came into being years ago, because this is what was being done for all cells. Note how for that example, you didn't need to use |NumParts=2
. The reasoning for this is slightly unclear to me; I think it's to do with the long-deprecated Japanese episode lists, where titles where the only things there were multiples of, hence the row didn't need splitting. To generate actual split rows for the titles, see how the wikicode does it for
The Sandman (TV series)#ep11; we need to use |Aux1_1=
, |Aux1_2=
, ...|Director_1=
, |Director_2=
, ..., are used, then all cells after that are split by default. So if you duplicated the table above, but copied the formatting from The Sandman as linked, and used |Aux1_1=
and |Aux1_2=
to actually split the titles, you'd find that |Aux3=
and |OriginalAirDate=
would also split. --
Alex_21
TALK
20:10, 7 March 2023 (UTC)
|EpisodeNumber=
and then helping span info as needed correctly, however that is accomplished. -
Favre1fan93 (
talk)
16:14, 8 March 2023 (UTC)
So I don't know if I'm doing something wrong, but this is what happens when I try to use |Title_1=
and |Title_2=
with the new code:
Extended content
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
InfiniteNexus ( talk) 17:59, 10 March 2023 (UTC)
<hr>
. --
Alex_21
TALK
01:02, 11 March 2023 (UTC)
No. overall |
No. in season | Title | Directed by | Written by | Storyboard by | Original air date |
Prod. code | U.S. viewers (millions) |
---|---|---|---|---|---|---|---|---|
1 | 1 | " Anne or Beast?" | Bert Youn | Matt Braly & Jack Ferraiolo | Kyler Spears, Yonatan Tal & Bert Youn | June 17, 2019[nb 1] | 103 | 0.39 |
"Best Fronds" | Derek Kirk Kim | Aaron Austin & Hannah Ayoubi | ||||||
@
Alex 21: One final thought regarding this now. I think there could be a benefit to potentially darkening the grey lines to delineate "part" episodes in the transcluded tables or tables that don't use |Line Color=
much like you do with {{
Series overview}}. If you look at
List of Agents of S.H.I.E.L.D. episodes#Season 5 (2017–18) and
Marvel Studios: Legends, you can see how (especially with Legends) it is a bit harder to make out the groupings. -
Favre1fan93 (
talk)
15:48, 11 March 2023 (UTC)
|BottomColor=color
, that when optionally used, forces the line color to be shown with or without a summary and even in transclusion. (FWIW, #A2A9B1 is the table border default, and #8D939A is what is used as the darker color in overviews.) |BottomColor=
would then override |LineColor=
, since you can't have two border colours at the same time. Thoughts? --
Alex_21
TALK
23:12, 11 March 2023 (UTC)
References
Notes
@
Alex 21,
Alexiaa,
AussieLegend,
Frietjes,
GKFX,
Gonnym,
Izkala,
Izno,
Jackmcbarn,
John of Reading,
Johnuniq,
Jonesey95,
Lemondoge,
Markun,
Mr. Stradivarius,
MSGJ,
Plastikspork,
Pppery,
Primefac,
PrimeHunter, and
Xaosflux: please see
Wikipedia talk:WikiProject Television#Refnotes in transcluded episode summaries. The issue mentioned there describes {{
efn}}
, but it also happens for <ref>...</ref>
. It appears to be
Template talk:Episode list/Archive 6#Bug with references in the ShortSummary, I don't know if it was not completely fixed at the time, or whether it was fixed and has since regressed. I hardly know any Lua, but quite a few people who presumably do know Lua have edited either
Module:Episode list,
Module:Episode list/sandbox or both since then. --
Redrose64 🌹 (
talk)
14:00, 25 June 2023 (UTC)
|ShortSummary=
argument, regardless of whether the short summary is included in the final output or not. When Lua accesses |ShortSummary=
, MediaWiki expands the wikitext in it, including any references contained, and hands the expanded wikitext to Lua. In doing so MediaWiki adds any references to the reference list, and leaves a
strip marker to denote where to add the superscript [1] link. If the Lua module chooses not to output the strip marker then the superscript link will not be displayed, but as the reference itself has already been added to the reference list, the reference will still be displayed regardless. The section to blame is this one:
-- Do not show the summary if this is being transcluded on the initial list page
-- Do include it on all other lists
if (onInitialPage and args.ShortSummary) then
local bottomWrapper = createShortSummaryRow(args, lineColor)
return tostring(root) .. tostring(bottomWrapper) .. trackingCategories
else
return tostring(root) .. trackingCategories
end
args.ShortSummary
exists before deciding whether to output the summary, you expand the argument's wikitext, and add the reference to the reference list. You could remove the phantom reference problem by changing the if statement to if (onInitialPage) then
; however, this would mean adding an empty table row if the |ShortSummary=
argument does not have any content in. Or you could add a separate parameter to decide whether to use the short summary, maybe |ShowShortSummary=no
, but this would clutter the parameter list. I'm not sure there's a great solution here. —
Mr. Stradivarius
♪ talk ♪
14:48, 25 June 2023 (UTC)
onInitialPage
before testing args.ShortSummary
seems like the best solution. I know in
Module:Sports table they were very careful to make sure that they only touched the args being used in the table to avoid showing phantom references when only part of the table was displayed. Thanks!
Plastikspork
―Œ(talk)
15:28, 25 June 2023 (UTC)Some edits at Module:Episode list on 20 June 2023 ( diff) by Gonnym added function addRowDividerTrackingCategory. That function evaluates every argument twice. Experiment shows that disabling the addition removes the current problems so I have done that ( diff). Asking at WT:WikiProject Television#Refnotes in transcluded episode summaries produced List of Agents of S.H.I.E.L.D. episodes as an example where the problem was visible. The problems appear to have gone. Before my edit, that article showed "Cite error: The named reference LunaBlaze was invoked but never defined (see the help page)." at ref 80 and the reported "Cite error: There are <ref group=lower-alpha> tags or {{efn}} templates on this page, but the references will not show without a {{reflist|group=lower-alpha}} template or {{notelist}} template (see the help page)." at the bottom of the page. Johnuniq ( talk) 07:57, 26 June 2023 (UTC)
|NumParts=
. I had been using the tracking category loaded into
AWB to address these. Would you be willing to take a look at addRowDividerTrackingCategory and debug/reinstate in order to continue? (If the evaluation of args.ShortSummary for |ShortSummary=
was the issue, this param does not need to be checked as there is no split of the field when |NumParts=
is used).
ButlerBlog (
talk)
15:29, 6 July 2023 (UTC)
|NumParts=
to separate multiple values into rows. For example, in this one
[1] there were a couple of 2 part episodes where the season and overall series values were on a single line, but split by an hr tag. This should have used NumParts and a _1/_2 value for the episodes. Similar examples, but with other fields are
[2] &
[3]. As noted in
the discussion above this one, using the hr instead of the multipart approach results in an accessibility issue and we want to use a maintenance category to identify these so they can be cleaned up and monitored going forward. As you probably know, the
Television project uses maintenance categories to track the use of various templates the project articles use in order to fix these problems, so what @
Gonnym had placed in there was to identify when this formatting exists so it can be monitored for fixing by project members. I actually trust Gonnymn's knowledge of the module as they've worked extensively on
the various maintenance categories in the TV project for this module as well as others (
Template:Infobox television and others). Hope that gives some clarification. TIA for any input you may have.
ButlerBlog (
talk)
15:50, 7 July 2023 (UTC)
hastemplate:"Episode list" insource:/EpisodeNumber[ -~]*\<hr/
. The problem with the proposed code (which I removed) is that it evaluates every parameter regardless of whether the parameter ends up being used. If a parameter includes a ref, evaluating it will generate a reference error. I'll try to examine the code and see where it uses specific parameters—they could be checked.
Johnuniq (
talk)
08:53, 9 July 2023 (UTC)
It seems like it doesn't emit footnotes given in the Rtitle
paramteter. One example is
Atomic Puppet, which tries to use a reference named "auto" on the "Brawl for all!" episode. That reference isn't emitted, subsequent inovcations for fotnotes aren't emitted, and later an error is emitted because "auto" isn't defined. @
MSGJ:, @
The Mol Man:, I don't see any code in the new LUA implementation that handles rtitle
, and there are no /testcases. Should this conversion be reverted until it can be made to work correctly? --
Mikeblas (
talk)
19:22, 13 July 2023 (UTC)
Rtitle
will not adda footnote to Title_1
and that RTitle_1
is necessary. --
Mikeblas (
talk)
19:30, 13 July 2023 (UTC)
I have made a change to the sandbox to let mobile users read the description without having to scroll sideways if there's too many columns in the header to fit horizontally on one thin mobile screen. Specifically, wrapping the description text in a div and setting the max-width of that div to 90vw (90% of the viewport (window) size). View Template:Episode list/testcases on mobile to see what i'm talking about, or even resize the window to be thin on a computer.
With the Vector 2010 skin on computer, because it goes on total window size, it is "off" by the amount of the left sidebar, not relevant with mobile or Vector 2022 because there's no sidebar, but IMO its less of an issue with a resizable browser window than a fixed width mobile device.
Its very clear on the pokemon episode 1 row (live you have to scroll right to read the whole description, sandbox you don't). The good part of it is you can scroll right if you want to see more of the information in the header, so the template doesn't have to be remade for mobile (i.e. you could also make it so the columns go vertically on mobile but that's kind of unwieldy).
It seems to work with testcases, can someone look it over and see if its good? I'm not 100% sure if 90vw is the right size, it might need tweaking and further testing. I really don't want to have to scroll right to read episode descriptions anymore lol. MarkiPoli ( talk) 12:15, 2 October 2023 (UTC)
Greetings and felicitations. The "TranslitTitle" fields are outputting the label "Transcription" rather than the accurate "Transliteration", as seen in Kyō Kara Ore Wa!! § "Episodes" Would you please be so kind as to change this? — DocWatson42 ( talk) 04:12, 13 November 2023 (UTC)
The module underlying this template says
Line 1: <Title><RTitle> (with no space between) Line 2: <AltTitle><RAltTitle> (with no space between) OR Line 2: Transcription: <TranslitTitle> (<Language>: <NativeTitle>)<RAltTitle> (with space between first two parameters)
But normal presentation expected would be
Further the output outputs a linked language name, contributing to overlinking in the article. GraemeLeggett ( talk) 21:17, 16 January 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: Change from outputting "transcription" under native title to "transliteration" Diff:
− | + | "transliteration" |
GraemeLeggett ( talk) 21:06, 16 January 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change:
Per
Wikipedia:Manual_of_Style/Japan-related_articles#General_guidelines, referrring to
Wikipedia:Manual_of_Style#Foreign_terms transliterated text should be italicised, currently it is not. The display code needs to be changed to italicise the output from the | TranslitTitle =
parameter
Diff: So when applied to first episode listed at Full_Dive#Anime
Should render as
GraemeLeggett ( talk) 19:38, 17 January 2024 (UTC)
Deactivating edit request as weeks in there still seems to be no agreement on any specific change to be made. Please come to an agreement, code it in the sandbox, and, if you still need an uninvolved template editor to implement, reactivate the request. * Pppery * it has begun... 02:56, 6 February 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
When Guests and MusicalGuests were originally requested here, there was a requirement that they would be aliases of Aux1 and Aux2 and would not be able to be used at the same time, which is indicated by a comment in the code: Module:Episode_list#L-57. But in fact they freely coexist separately as independent parameters (also being undocumented):
aux1 | aux2 | aux3 | Guest(s) | Musical/entertainment guest(s) |
---|---|---|---|---|
Aux1 | Aux2 | Aux3 |
I still think it should be the way it was originally intended to be. That it is, they should be aliases for Aux1 Aux2, created simply to force predefined headings. Solidest ( talk) 12:43, 7 February 2024 (UTC)
Discussion at Talk:List of Hunter Street episodes about whether to include writers and directors, any thoughts please. Thanks, Indagate ( talk) 09:42, 12 March 2024 (UTC)
There seems to be some problem with this template. Short summaries are no longer visible. I'm assuming this isn't deliberate? Skteosk ( talk) 21:55, 30 March 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: The short summary section of this template does not appear to being showing up on any pages. I have checked multiple different TV shows on different browsers and the Wikipedia App. Zachary Sikes ( talk) 03:45, 31 March 2024 (UTC)
In cleaning out the mess I made with the whole episode move thing, and as an extension of
#Fault? above, could we get a tracking parameter set up for the /sublist template for when |1=
is provided but doesn't match the pagename?
Primefac (
talk)
08:50, 1 April 2024 (UTC)
|1=
parameter is "Attack on Titan season 1" (and because the page and parameter match, the episode summaries are shown), but when that episode table is transcluded to
List of Attack on Titan episodes, the |1=
parameter will still be "Attack on Titan season 1" (and because the page and parameter don't match, the episode summaries are hidden). --
Alex_21
TALK
09:07, 1 April 2024 (UTC)
![]() | This is an archive of past discussions. 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 | ← | Archive 5 | Archive 6 | Archive 7 |
Please take a look at the sandbox and testcases. I've updated the code with the following changes:
|TranslitTitle=
, |NativeTitle=
and |NativeTitleLangCode=
. This should enable us to remove {{
Japanese episode list}} per the merge result and correctly handle non-English languages, as the module now uses
Module:Lang for these languages.|NumParts=
and |Title_n=
parameters. This should enable us to remove {{
Japanese episode list multi-part}}.|NumParts=
and |Serial=
.|EpisodeNumber=
was not used.There should be no bugs still in the code, but test it out and let me know if you have any comments. -- Gonnym ( talk) 17:41, 16 January 2019 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
As requested above, would appreciate if any template editor can verify my code on Module:Episode list/sandbox throws no errors. -- Gonnym ( talk) 07:16, 28 January 2019 (UTC)
In "Double episodes", the Live template shows "22, 24" and the Sandbox shows "22–24", which has a different meaning (i.e. 22, 23, and 24). Is this change intentional? Other than these two minor problems, the rest of the test cases look perfect to me. – Jonesey95 ( talk) 15:59, 30 January 2019 (UTC)
Any other comments? Did anyone see any errors in the code on main-space pages? -- Gonnym ( talk) 12:12, 3 February 2019 (UTC)
|1=
- For TemplateData there is no such thing as an unnamed parameter and it treats all unnamed parameters as numbered parameters. So |1=
is necessary for the documentation. Since
Template:Episode list/sublist was setup to use this documentation page, and that template needs it, not a lot I can do here. However, as I've noted
here, if the usage of this parameter is only used in one of these templates and not both, I can eliminate the need for it altogether and get that data without user input.|1=
.|1=
and unnamed is the same thing - it's not a change in the code or something (accessing an unnamed parameter in lua is accessing it from the numbered/position its placed). Not really sure what change you want me to make in the documentation.The WMF asserts that its policies "may not be circumvented, eroded, or ignored by Wikimedia Foundation officers or staff nor local policies of any Wikimedia project- are you sure you want to get into this? (regarding your question about the incorrectly placed values, the next sentence I wrote has that answer - you're adding a story arc title AND episode title in the same field - that is mashing two distinct fields into one) -- Gonnym ( talk) 17:15, 4 February 2019 (UTC)
|1=
used in tables that aren't transcluded? It isn't, and thus shouldn't be used in the documentation. And I'm aware that it's the same thing, but they are used differently. I've never seen {{
Episode list/sublist|(newline)1=Article}}
, only ever {{
Episode list/sublist|Article}}
.|1=
or you can use it without it - it is the same thing when invoking a template. The documentation still needs to call it "1" as you can't call an unnamed parameter unnamed. This is a rather pointless argument. Also, I find it amazing that a veteran editor like yourself knowingly ignores accessibility issues and the actual point in that policy which states that I actually do not need a consenous to point out that your usage in the Doctor Who articles is incorrect. Pretty amazing Alex. --
Gonnym (
talk)
00:55, 5 February 2019 (UTC)
|1=
. But I agree, it is pointless, so I'll update the documentation accordingly. And truly, I live to amaze; if you want to change the articles from their standing layouts, I'll be there to restore and wait for a discussion. Cheers. -- /
Alex/
21
01:04, 5 February 2019 (UTC)
The onus is on you if you want to create a consensus to change that, and if another editor implements improvements to eliminate theAvoid using
<br>
tags in adjacent cells to emulate a visual row that isn't reflected in the HTML table structure. This is a problem for users of screen readers which read tables cell by cell, HTML row by HTML row, not visual row by visual row.
<br>
tags, any reversion will certainly be viewed as
disruptive editing. Is that clear enough for you? --
RexxS (
talk)
16:47, 5 February 2019 (UTC)
<hr>
. Same layout given, no <br>
tag, no issues in DTAB with <hr>
, and quite fitting as this module already uses <hr>
to split rows. -- /
Alex/
21
22:35, 5 February 2019 (UTC)
<hr>
used either, then state a policy that bans it and/or remove it from this module as well. -- /
Alex/
21
23:33, 5 February 2019 (UTC)
<hr>
or <div>...</div>
or <p>...</p>
or any other block-level html to put text on new lines within a table cell produces exactly the same problem for a screen reader user. --
RexxS (
talk)
00:02, 6 February 2019 (UTC)
"website developer in my spare time". Any web developer worth their salt understands accessibility issues; you can start at WCAG. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:10, 6 February 2019 (UTC)
Directed here from
Wikipedia talk:WikiProject Doctor Who#Season articles layout change. Clear improvement to align with site-wide consensus at
WP:DTAB, which the Doctor Who project is currently violating. Pleased to learn that <br>
should not be used going forward for the benefit of those using screen readers. No objections at all to the proposed changes.
U-Mos (
talk)
03:20, 7 February 2019 (UTC)
On another interesting note, why the separate rows for identical directors and writers, but a rowspan for the title? An Unearthly Child applies to the whole serial, as does the director and writer, Waris Hussein and Anthony Coburn. Same for the production code. -- / Alex/ 21 03:52, 7 February 2019 (UTC)
<hr>
tag is acceptable for the multi-title example, then that means that the Doctor Who articles can indeed use the <hr>
tag instead of <br>
. [T]here should be no problem that I can foresee.-- / Alex/ 21 08:41, 7 February 2019 (UTC)
[a]s long as whoever uses that technique understands that a screen reader will effectively ignore the horizontal rule and will read out the entire contents of that table cell as if the rule wasn't there, then there should be no problem that I can foresee.No comment was made in that thread discerning the use of
<hr>
in only a singular column vs. multiple columns. If it can be used in one column, why can it not be used in multiple columns? Or, on the other hand, if it cannot be used in multiple columns, why can it be used in one column? -- /
Alex/
21
09:05, 7 February 2019 (UTC)
Title |
---|
Galaxy 4 |
Four Hundred Dawns |
Trap of Steel |
The Exploding Planet |
Air Lock |
Title |
---|
Galaxy 4 Four Hundred Dawns Trap of Steel The Exploding Planet Air Lock |
Title | Air date |
---|---|
Galaxy 4 | |
Four Hundred Dawns | 11 September 1965 |
Trap of Steel | 18 September 1965 |
The Exploding Planet | 25 September 1965 |
Air Lock | 2 October 1965 |
Title | Air date |
---|---|
Galaxy 4 Four Hundred Dawns Trap of Steel The Exploding Planet Air Lock |
11 September 1965 18 September 1965 25 September 1965 2 October 1965 |
How do the updates solve the accessibility problems of using block elements like those seen at Agents of S.H.I.E.L.D. (season 2)#ep43, List of Unbreakable Kimmy Schmidt episodes#ep48, Big Mouth (TV series)#ep21 and/or Once Upon a Time (season 4)#ep74? -- / Alex/ 21 11:54, 20 February 2019 (UTC)
|DifferentDirectors=
and |DifferentWriters=
parameters, which when set to true, will check for DirectedBy_# and WrittenBy_# parameters. Does this work for what you need? --
Gonnym (
talk)
08:33, 24 February 2019 (UTC)
|Serial=
. If there are other styles that work differently, then if needed I'll change the code to this setup. Let me know what's needed, and if I need to change something or add the sandboxed code. --
Gonnym (
talk)
09:12, 24 February 2019 (UTC)
|WrittenBy_1=
, |WrittenBy_2=
and |WrittenBy_3=
but only |DirectedBy_1=
and |DirectedBy_2=
, there is no way to know what the editor meant by that and the system shouldn't be used for guessing. So in this case |NumParts=
should still be used and all para# parameters should have the matching number of entries. Other than that I think it could work. Will have time later to work on it. --
Gonnym (
talk)
10:26, 24 February 2019 (UTC)
|DirectedBy_3=
with {{
TableTBA}}, as empty cells currently and already are, and add the article to a tracking category. I'll see if I can implement some sandbox changes and whip up some test cases. -- /
Alex/
21
10:29, 24 February 2019 (UTC)|Serial=
and |NumParts=
; the less parameters to deal with, the better. -- /
Alex/
21
11:38, 24 February 2019 (UTC)
|NumPart=
parameter, as you are looping over 100 entries for each column, while the values could be 2 or 3. Rest of the code seems good. --
Gonnym (
talk)
12:13, 24 February 2019 (UTC)
|NumParts=
; guess it is better to keep that. Still working out the multiple titles issue, not sure why that's erroring. -- /
Alex/
21
23:23, 24 February 2019 (UTC)Dear Admins,
The short summary is not appearing on my page no matter what? Kindly help me figure out what i am doing wrong? Page is Draft:The Fish'n Canada Show Thank You! -- KoolKrazy ( Talk To Me!)
Gonnym, I had to revert the most recent change because it added several articles to Category:Pages with script errors including List of Good Mythical Morning episodes, List of Horizon episodes, The Dr. Oz Show, and List of The Nature of Things episodes. I imagine it's due to the string processing on very large input. perhaps if these pages are fixed, we can add the tracking back again? Frietjes ( talk) 22:02, 25 October 2019 (UTC)
Per the ongoing discussion at
TfD there is some desire to add |Guests=
and |MusicalGuests=
as an alternative to using the less obvious |Aux1=
and |Aux2=
in the ca. 106 pages using {{lnep}}
. are there any objections to adding these parameters?
Frietjes (
talk)
18:16, 6 December 2019 (UTC)
How is the id parameter set on a table row created with Episode list to create a row anchor for a sectionlink, see Help:Table#Section link or map link to a row anchor? Jim Craigie ( talk) 17:24, 28 November 2019 (UTC)
row:tag('th')
:attr('scope', 'row')
:attr('rowspan', numberOfParameterGroups)
:attr('id', 'ep' .. idTrim(idTrim(episodeNumber, ' ----'), '<'))
:css('text-align', 'center')
:wikitext(episodeText)
row:tag('td')
:attr('id', 'pc' .. idTrim(idTrim(args.ProdCode, ' ----'), '<'))
:css('text-align', 'center')
:wikitext(args.ProdCode)
|EpisodeNumber=
uses <hr />
or <br />
(or any other HTML tag), then the anchor is the first number. If the |EpisodeNumber=
uses –
(or anything else), then the anchor is whatever is displayed/used.1<hr>2
is #ep1
, the anchor to 1–2
is #ep1–2
, and the anchor to 1–2
(as the example article previously used) would literally be #ep1–2
(see
Special:Permalink/927849664#ep1–2 ). -- /
Alex/
21
23:57, 28 November 2019 (UTC)
#ep1–2
does not work – it actually has to be #ep1&ndash;2
not just for display, but to make the link work.
Jim Craigie (
talk)
05:48, 29 November 2019 (UTC)
If you are updating Episode list would it be possible to create a third ID containing the |Title=
parameter value – it would be much easier to use than having to find the episode number (and its format, which may change invalidating links – if anyone had previously created links into Silent Witness episodes using
Alex's solution then
IJBall's edit tonight has just invalidated them all!), and production numbers don't exist publicly for UK productions?
Jim Craigie (
talk)
06:30, 29 November 2019 (UTC)
@ Alex 21:, while we are fixing issues with the episode ID, do you have any idea for a solution for cases where we have a specials or webisode table? List of Heroes episodes as an example. Can't like to any specific episode, is they share the anchor with regular episode. -- Gonnym ( talk) 08:28, 29 November 2019 (UTC)
{{
Episode table}} now supports |anchor=
which allows duplicate numbering on the same page. See doc for more info. --
Gonnym (
talk)
06:25, 13 January 2020 (UTC)
Where is the raw code for this template so that some people have the ability to use it on other mediawiki sites? — Preceding unsigned comment added by 69.137.181.135 ( talk) 17:48, 14 January 2020 (UTC)
Has any thought ever been given to adding an optional parameter for episode lengths? With an increasing number of shows where this varies, seems it would be useful information to tabulate in some cases. U-Mos ( talk) 21:20, 7 February 2020 (UTC)
Is there anything that can be done about the way this template displays on mobile? Someone posted this screenshot on Reddit: instead of wrapping the text, it merely cuts it off and nothing can be done to scroll over and view it. Adding a scrollbar would be just as ugly, but can't the table width be set to fit the window and automatically wrap? Thanks. —Мандичка YO 😜 16:21, 9 March 2020 (UTC)
nothing can be done to scroll over and view it. Additionally, I don't really think there's anything that can be done because the table inherently is larger in px width than your standard mobile phone display. - Favre1fan93 ( talk) 17:02, 9 March 2020 (UTC)
I don't think the template should automatically fill in "TBA" and "TBD" for empty values. That sort of assertion is not encyclopedic. The template should only list information that's available without guesswork about something that "will be announced" or "will be determined." Some episodes are many decades old and the missing information will never be announced or determined. Even with new shows, it's presumptuous that some missing information will be announced or determined. NameMyRemember ( talk) 09:17, 24 March 2020 (UTC)
The template has no parameter for 'Duration' or 'Total length'. I think it should be, as it's useful for many users like me. Thank you. Empire AS Talk! 08:27, 31 July 2020 (UTC)
Seems to be broken right now. 2601:14F:4500:4300:E56D:E54A:DAA7:549B ( talk) 07:50, 4 August 2020 (UTC)
Without | EpisodeNumber field, title becomes bold. See for example List_of_Sailor_Moon_episodes#Shorts. Smeagol 17 ( talk) 11:12, 3 September 2020 (UTC)
Hello maintainers 👋
While editing Elmo's World, I noticed that the background to references added for accessibility looks different on Chrome than they did in Firefox. The result does not look good and is not accessible as roughly half of the reference does not have a high contrast.
I took a crack at modifying the inline CSS and was able to get it to look good in Chrome but but it subsequently broke it in Firefox.
Some things we could consider to fix this is:
I'd be happy to work on this, but I'd appreciate some input first. — motevets ( talk) 15:51, 15 September 2020 (UTC)
I think the TBA default entry should be removed or replaced by a dash. It shows up in episode lists of old shows where the director and/or writer are unknown or information hasn't yet been entered into the article. That is clearly not the same thing as "to be announced". 93.136.110.156 ( talk) 06:40, 4 December 2020 (UTC)
{{
TableTBA|N/A}}
. -- /
Alex/
21
02:05, 10 December 2020 (UTC)It would be great if the module could get data like title, director, screenwriter, etc. from Wikidata if not specified in the article. For example on The No. 1 Ladies' Detective Agency (TV series)#TV series (2009) I could write
{{Episode list|qid=Q102864920}}
and all relevant data would be read from Wikidata. Apart from the summary (which would need to remain in the article) most of the other fields are supported in Wikidata — Martin ( MSGJ · talk) 20:05, 4 December 2020 (UTC)
Not sure if this has been discussed before, but is there a reason why there is no EpisodeNumber_1, EpisodeNumber_2, EpisodeNumber2_1, EpisodeNumber2_2, etc.? - adamstom97 ( talk) 08:08, 9 December 2020 (UTC)
<hr>
to separate episode numbers (as the only usage for that tag is a "visual" separation), we can just use dashes for episode numbers, as it shows the spanning range. -- /
Alex/
21
02:08, 10 December 2020 (UTC)
<hr>
). -
adamstom97 (
talk)
07:03, 10 December 2020 (UTC)Despite having a mobile website (that still looks completely different to the desktop website) for some years now, this template hasn't been updated to work well on phones. Sticking prose into a table that requires constant side-to-side scrolling on narrow screens isn't a great idea. List of Not Going Out episodes is a particularly awful example of this. Why is the Wikipeedia "community" so consistently uncaring about half your readership? Perhaps one of the 'template editors' could do some template editing to bring this template into the 2010s (a decade late). Oh, DrPizza! ( talk) 02:57, 11 January 2021 (UTC)
uncaringabout being polite to your fellow editors and template editors? -- / Alex/ 21 04:37, 11 January 2021 (UTC)
ShortSummary
parameter. This causes the text to wrap to the width of the table, which on phones is often wider than the width of the screen. So a solution would seem to be to remove the non-tabular data from being inside a table. Let tables be used for the tasks they were designed for instead of doing double duty as a (poorly-working for half your readership) container for a paragraph or two of text.Yawn.Are you bored? That would be a shame. I thought you enjoyed being a pugnacious wikisoldier. Well, participating in this discussion is entirely optional. Oh, DrPizza! ( talk) 03:58, 17 January 2021 (UTC)
As for the issue of side-to-side scrolling, there is no way to resolve this other than to remove the summaries altogether.As stated, the prose summaries should be taken out of a table and put into compliance with your own MOS. Something like this. The separate episode "rows" can still be combined into a consolidated table:
Something like this.God, that's horrifying and a complete violation of tabular formatting and accessibility policies. Absolutely not. Thanks for the suggestion but let's take a heavy pass. I can guarantee you're going to get 0% consensus from any WikiProject for that. I mean, you're welcome to try, though. Go for it. -- / Alex/ 21 04:02, 17 January 2021 (UTC)
I have a question regarding the first example under Template:Episode list#Non-English titles. Following WP:ROMAJI, I was expecting it to be written "Pokémon", because that is the common English name, based on the title and text of the article Pokémon. Custardbandlers says following WP:ROMAJI it should be "Pokemon" because that's the Hepburn romanization. Which is correct? Thanks! -- Beland ( talk) 04:28, 5 March 2021 (UTC)
There's no explanation of what Episode list/sublist is for in the documentation. There are usage examples but no clear description of it's purpose. What is the purpose of sublist? - X201 ( talk) 07:49, 23 April 2021 (UTC)
The episode table at Seabound_(Ninjago_season)#Episodes is behaving strangely, and I can't figure out why. The Viewers parameters are empty, and the template adds "N/A" to the Viewers column for episodes 1 thru 6, but adds "TBD" to episodes 7 thru 16. Any ideas?— TAnthony Talk 16:18, 19 May 2021 (UTC)
|Viewers={{TableTBA|TBD}}
. -- /
Alex/
21
21:20, 19 May 2021 (UTC)Episode guides are still painful to read on mobile because the episode metadata columns are too wide, forcing the description field to be wider than the screen, such that you have to scroll horizontally back and forth to read them. This screenshot from a tweet 6+ years ago shows the problem that still exists today: https://twitter.com/jelsert/status/659548147086204928
It's 2022, and the rest of the web has solved this with responsive web design a decade ago. What would it take to fix this? It would require updating the CSS, but I have no idea who is responsible for that, or how we could encourage that? -- ToastyKen ( talk) 03:46, 11 February 2022 (UTC)
Hello! Recently I was editing
Jay Leno's Garage#Compilation (2020) to make the "Number overall" display as N/A instead of TBA since they aren't considered to be part of the main series and therefore don't have a number overall. I was forced to use /
instead of "/" as in the "episode number" parameter, the "/" character is displayed as an en/em-dash (I don't know what the difference is at first glance, all I know is one is longer). Any reason why it does this? ―
Blaze Wolf
TalkBlaze Wolf#6545
18:27, 14 March 2022 (UTC)
The title of an episode might be a more natural heading for the row in table. It also provides the link to the standalone article, if it exists, so would give this link more prominence at the beginning of the row. I will try and provide some examples of how it might look. — Martin ( MSGJ · talk) 21:32, 11 May 2022 (UTC)
No. overall |
No. in series | Title | Location | Directed by | Original air date | UK viewers (millions) |
---|---|---|---|---|---|---|
13 | 1 | " The Devil of Christmas" | Alpine chalet | Graeme Harper | 27 December 2016 | 1.03 |
Title | No. in series |
Location | Director | Original air date | UK viewers (millions) |
---|---|---|---|---|---|
" The Devil of Christmas" | 1 | Alpine chalet | Graeme Harper | 27 December 2016 | 1.03 |
Related to proposal above, I think it would be clearer, more semantic and accessible if the heading cell of each episode spanned the plot summary too. Then it would be more obvious which episode the summary related to. Mock up will be posted below. — Martin ( MSGJ · talk) 12:04, 12 May 2022 (UTC)
Title | No. in series |
Location | Director | Original air date | UK viewers (millions) |
---|---|---|---|---|---|
" The Devil of Christmas" | 1 | Alpine chalet | Graeme Harper | 27 December 2016 | 1.03 |
In a film within the episode, an English family (Pemberton, Rula Lenska, Jessica Raine and George Bedford) travel to an Austrian chalet in December 1977. They are told the story of the Krampus by their guide (Shearsmith). Meanwhile, the film's director ( Derek Jacobi) provides audio commentary. |
The description for ShortSummary is that it be a plot summary. There has been, and continues to be, a trend towards including additional information as "notes" and I've seen this from new and experienced editors alike. Where do we draw the line on what's appropriate and what's not, and should the parameter description be a little more clear on what's allowed? I think it's obvious when it's trivia. For example, I recently removed a "note" that was describing a stock footage scene in The Waltons that was also used by Gilligan's Island. But there are other less obvious situations, especially when it comes to cast. We do see a lot of guest cast noted in the ShortSummary, which I think is an appropriate place to note specific cast additions. But sometimes this gets extended to information about So-and-so appears but is not credited, or So-and-so is credited but does not appear; and for a series that uses stock credits, that can get tedious for minor characters who are in the standard credits but do not appear in every episode. Am I being too rigid in trying to figure out a bright line on this? ButlerBlog ( talk) 14:30, 23 September 2022 (UTC)
Currently, if a parameter is included (such as |DirectedBy=
) with no content, "TBA" will fill the cell. However, this doesn't necessary make sense for episodes that have not filled in the parameter after its air date. In that case, it should be "N/A" or perhaps a "–". Is this possible to add in a check against whatever is placed in the "airdate" parameter, and make it be TBA for a future episode, and "N/A" or "–" for a past one? See
A Touch of Grace, a show from the 1970s with a number of unfilled in parameters, as an example where this is a problem. -
Favre1fan93 (
talk)
21:45, 18 September 2022 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
@ Alex 21: This causes Lua errors if there's no original air date set, for example at List of Makutano Junction episodes. Please revert or fix this. -- rchard2scout ( talk) 12:41, 26 September 2022 (UTC)
Because these tables can get pretty wide, I often notice that the ShortSummary text is stretched beyond the width of a mobile device screen. The result is a poor experience on mobile where you have to swipe the screen left and right to read across the lines of the paragraph.
You should consider limiting the width of the text in the ShortSummary cell to the width of the viewport on mobile. Something like a max-width
of 90vw
would make it a lot easier for mobile users to read the summaries.
DrewBino
talk (
afc0703)
01:39, 31 January 2023 (UTC)
Per consistency with other multipart episode parameters that have been added to this template, I propose we also use EpisodeNumber_1, EpisodeNumber_2, EpisodeNumber2_1, and EpisodeNumber2_2. Many episode lists currently use <hr>
to split episode numbers, which has been objected to by
User:Alex 21 for accessibility reasons (see our own
user talk discussion), so these further NumParts additions would address those concerns. The residual dashes which are still used in certain episode lists are really less clear visually – especially the cases where directors/writers are only credited in part 1 or part 2 specifically – and the dashes are inconsistent with the visual grammar of presenting all other episode numbers vertically. Discovered this idea was
previously floated two years ago by
User:Adamstom.97, and I agree this should be implemented. --
Wikipedical (
talk)
20:46, 6 December 2022 (UTC)
Hey @ Alex 21: Could you look into this? Thanks. InfiniteNexus ( talk) 16:57, 31 January 2023 (UTC)
I've had the day off, so I thought I'd give it a crack to see what I would get. Let's analyze the following results:
No. overall |
No. in season | Title | Directed by | Written by | Original air date | U.S. viewers (millions) |
---|---|---|---|---|---|---|
43 | 21 | " S.O.S." | Vincent Misiano | Jeffrey Bell | May 12, 2015 | 3.88 |
43 | 21 | " S.O.S." | Vincent Misiano | Jeffrey Bell | May 12, 2015 | 3.88 |
Billy Gierhart | Jed Whedon & Maurissa Tancharoen | |||||
43 44 | 21 22 | " S.O.S." | Vincent Misiano | Jeffrey Bell | May 12, 2015 | 3.88 |
Billy Gierhart | Jed Whedon & Maurissa Tancharoen | |||||
43 | 21 | " S.O.S." | Vincent Misiano | Jeffrey Bell | May 12, 2015 | 3.88 |
44 | 22 | Billy Gierhart | Jed Whedon & Maurissa Tancharoen | |||
However, this new fourth example then leads me to the following observation. Notice how the airdate and viewers cells are also split, despite having equal values. The reasoning for this in the past has been that, if we have a cell that's single-spanning, all cells afterwards must also be single-spanning (i.e. we cannot have a multiple-spanning cells after single-spanning cells), due to "accessibility reasons". However, I've never seen any contributing support or documentation for this, and if we were to implement these edits, then we have single-spanning episode numbers and a multiple-spanning title following. This has also never been an issue for spanning cells in {{ Series overview}} (e.g. List of Star Trek television series), so after this edit, I would suggest that we implement the merging of those equal-valued cells to be multiple-spanning rather than duplicated single-spanning cells. -- Alex_21 TALK 05:04, 7 March 2023 (UTC)
No. overall |
No. in season | Title | Associated MCU work | Original release date |
---|---|---|---|---|
1 2 | 1 2 | "Wanda Maximoff" | WandaVision | January 8, 2021 |
"Vision" | ||||
|Title_1=
, |Title_2=
, ..., are used, they don't generate a split cell, and instead just use <hr>
between the titles, meaning none of the cells above are actually spanning, they're just all, by default, spanning one row. They're visually split, yes, which is where and why all the accessibility discussions came into being years ago, because this is what was being done for all cells. Note how for that example, you didn't need to use |NumParts=2
. The reasoning for this is slightly unclear to me; I think it's to do with the long-deprecated Japanese episode lists, where titles where the only things there were multiples of, hence the row didn't need splitting. To generate actual split rows for the titles, see how the wikicode does it for
The Sandman (TV series)#ep11; we need to use |Aux1_1=
, |Aux1_2=
, ...|Director_1=
, |Director_2=
, ..., are used, then all cells after that are split by default. So if you duplicated the table above, but copied the formatting from The Sandman as linked, and used |Aux1_1=
and |Aux1_2=
to actually split the titles, you'd find that |Aux3=
and |OriginalAirDate=
would also split. --
Alex_21
TALK
20:10, 7 March 2023 (UTC)
|EpisodeNumber=
and then helping span info as needed correctly, however that is accomplished. -
Favre1fan93 (
talk)
16:14, 8 March 2023 (UTC)
So I don't know if I'm doing something wrong, but this is what happens when I try to use |Title_1=
and |Title_2=
with the new code:
Extended content
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
InfiniteNexus ( talk) 17:59, 10 March 2023 (UTC)
<hr>
. --
Alex_21
TALK
01:02, 11 March 2023 (UTC)
No. overall |
No. in season | Title | Directed by | Written by | Storyboard by | Original air date |
Prod. code | U.S. viewers (millions) |
---|---|---|---|---|---|---|---|---|
1 | 1 | " Anne or Beast?" | Bert Youn | Matt Braly & Jack Ferraiolo | Kyler Spears, Yonatan Tal & Bert Youn | June 17, 2019[nb 1] | 103 | 0.39 |
"Best Fronds" | Derek Kirk Kim | Aaron Austin & Hannah Ayoubi | ||||||
@
Alex 21: One final thought regarding this now. I think there could be a benefit to potentially darkening the grey lines to delineate "part" episodes in the transcluded tables or tables that don't use |Line Color=
much like you do with {{
Series overview}}. If you look at
List of Agents of S.H.I.E.L.D. episodes#Season 5 (2017–18) and
Marvel Studios: Legends, you can see how (especially with Legends) it is a bit harder to make out the groupings. -
Favre1fan93 (
talk)
15:48, 11 March 2023 (UTC)
|BottomColor=color
, that when optionally used, forces the line color to be shown with or without a summary and even in transclusion. (FWIW, #A2A9B1 is the table border default, and #8D939A is what is used as the darker color in overviews.) |BottomColor=
would then override |LineColor=
, since you can't have two border colours at the same time. Thoughts? --
Alex_21
TALK
23:12, 11 March 2023 (UTC)
References
Notes
@
Alex 21,
Alexiaa,
AussieLegend,
Frietjes,
GKFX,
Gonnym,
Izkala,
Izno,
Jackmcbarn,
John of Reading,
Johnuniq,
Jonesey95,
Lemondoge,
Markun,
Mr. Stradivarius,
MSGJ,
Plastikspork,
Pppery,
Primefac,
PrimeHunter, and
Xaosflux: please see
Wikipedia talk:WikiProject Television#Refnotes in transcluded episode summaries. The issue mentioned there describes {{
efn}}
, but it also happens for <ref>...</ref>
. It appears to be
Template talk:Episode list/Archive 6#Bug with references in the ShortSummary, I don't know if it was not completely fixed at the time, or whether it was fixed and has since regressed. I hardly know any Lua, but quite a few people who presumably do know Lua have edited either
Module:Episode list,
Module:Episode list/sandbox or both since then. --
Redrose64 🌹 (
talk)
14:00, 25 June 2023 (UTC)
|ShortSummary=
argument, regardless of whether the short summary is included in the final output or not. When Lua accesses |ShortSummary=
, MediaWiki expands the wikitext in it, including any references contained, and hands the expanded wikitext to Lua. In doing so MediaWiki adds any references to the reference list, and leaves a
strip marker to denote where to add the superscript [1] link. If the Lua module chooses not to output the strip marker then the superscript link will not be displayed, but as the reference itself has already been added to the reference list, the reference will still be displayed regardless. The section to blame is this one:
-- Do not show the summary if this is being transcluded on the initial list page
-- Do include it on all other lists
if (onInitialPage and args.ShortSummary) then
local bottomWrapper = createShortSummaryRow(args, lineColor)
return tostring(root) .. tostring(bottomWrapper) .. trackingCategories
else
return tostring(root) .. trackingCategories
end
args.ShortSummary
exists before deciding whether to output the summary, you expand the argument's wikitext, and add the reference to the reference list. You could remove the phantom reference problem by changing the if statement to if (onInitialPage) then
; however, this would mean adding an empty table row if the |ShortSummary=
argument does not have any content in. Or you could add a separate parameter to decide whether to use the short summary, maybe |ShowShortSummary=no
, but this would clutter the parameter list. I'm not sure there's a great solution here. —
Mr. Stradivarius
♪ talk ♪
14:48, 25 June 2023 (UTC)
onInitialPage
before testing args.ShortSummary
seems like the best solution. I know in
Module:Sports table they were very careful to make sure that they only touched the args being used in the table to avoid showing phantom references when only part of the table was displayed. Thanks!
Plastikspork
―Œ(talk)
15:28, 25 June 2023 (UTC)Some edits at Module:Episode list on 20 June 2023 ( diff) by Gonnym added function addRowDividerTrackingCategory. That function evaluates every argument twice. Experiment shows that disabling the addition removes the current problems so I have done that ( diff). Asking at WT:WikiProject Television#Refnotes in transcluded episode summaries produced List of Agents of S.H.I.E.L.D. episodes as an example where the problem was visible. The problems appear to have gone. Before my edit, that article showed "Cite error: The named reference LunaBlaze was invoked but never defined (see the help page)." at ref 80 and the reported "Cite error: There are <ref group=lower-alpha> tags or {{efn}} templates on this page, but the references will not show without a {{reflist|group=lower-alpha}} template or {{notelist}} template (see the help page)." at the bottom of the page. Johnuniq ( talk) 07:57, 26 June 2023 (UTC)
|NumParts=
. I had been using the tracking category loaded into
AWB to address these. Would you be willing to take a look at addRowDividerTrackingCategory and debug/reinstate in order to continue? (If the evaluation of args.ShortSummary for |ShortSummary=
was the issue, this param does not need to be checked as there is no split of the field when |NumParts=
is used).
ButlerBlog (
talk)
15:29, 6 July 2023 (UTC)
|NumParts=
to separate multiple values into rows. For example, in this one
[1] there were a couple of 2 part episodes where the season and overall series values were on a single line, but split by an hr tag. This should have used NumParts and a _1/_2 value for the episodes. Similar examples, but with other fields are
[2] &
[3]. As noted in
the discussion above this one, using the hr instead of the multipart approach results in an accessibility issue and we want to use a maintenance category to identify these so they can be cleaned up and monitored going forward. As you probably know, the
Television project uses maintenance categories to track the use of various templates the project articles use in order to fix these problems, so what @
Gonnym had placed in there was to identify when this formatting exists so it can be monitored for fixing by project members. I actually trust Gonnymn's knowledge of the module as they've worked extensively on
the various maintenance categories in the TV project for this module as well as others (
Template:Infobox television and others). Hope that gives some clarification. TIA for any input you may have.
ButlerBlog (
talk)
15:50, 7 July 2023 (UTC)
hastemplate:"Episode list" insource:/EpisodeNumber[ -~]*\<hr/
. The problem with the proposed code (which I removed) is that it evaluates every parameter regardless of whether the parameter ends up being used. If a parameter includes a ref, evaluating it will generate a reference error. I'll try to examine the code and see where it uses specific parameters—they could be checked.
Johnuniq (
talk)
08:53, 9 July 2023 (UTC)
It seems like it doesn't emit footnotes given in the Rtitle
paramteter. One example is
Atomic Puppet, which tries to use a reference named "auto" on the "Brawl for all!" episode. That reference isn't emitted, subsequent inovcations for fotnotes aren't emitted, and later an error is emitted because "auto" isn't defined. @
MSGJ:, @
The Mol Man:, I don't see any code in the new LUA implementation that handles rtitle
, and there are no /testcases. Should this conversion be reverted until it can be made to work correctly? --
Mikeblas (
talk)
19:22, 13 July 2023 (UTC)
Rtitle
will not adda footnote to Title_1
and that RTitle_1
is necessary. --
Mikeblas (
talk)
19:30, 13 July 2023 (UTC)
I have made a change to the sandbox to let mobile users read the description without having to scroll sideways if there's too many columns in the header to fit horizontally on one thin mobile screen. Specifically, wrapping the description text in a div and setting the max-width of that div to 90vw (90% of the viewport (window) size). View Template:Episode list/testcases on mobile to see what i'm talking about, or even resize the window to be thin on a computer.
With the Vector 2010 skin on computer, because it goes on total window size, it is "off" by the amount of the left sidebar, not relevant with mobile or Vector 2022 because there's no sidebar, but IMO its less of an issue with a resizable browser window than a fixed width mobile device.
Its very clear on the pokemon episode 1 row (live you have to scroll right to read the whole description, sandbox you don't). The good part of it is you can scroll right if you want to see more of the information in the header, so the template doesn't have to be remade for mobile (i.e. you could also make it so the columns go vertically on mobile but that's kind of unwieldy).
It seems to work with testcases, can someone look it over and see if its good? I'm not 100% sure if 90vw is the right size, it might need tweaking and further testing. I really don't want to have to scroll right to read episode descriptions anymore lol. MarkiPoli ( talk) 12:15, 2 October 2023 (UTC)
Greetings and felicitations. The "TranslitTitle" fields are outputting the label "Transcription" rather than the accurate "Transliteration", as seen in Kyō Kara Ore Wa!! § "Episodes" Would you please be so kind as to change this? — DocWatson42 ( talk) 04:12, 13 November 2023 (UTC)
The module underlying this template says
Line 1: <Title><RTitle> (with no space between) Line 2: <AltTitle><RAltTitle> (with no space between) OR Line 2: Transcription: <TranslitTitle> (<Language>: <NativeTitle>)<RAltTitle> (with space between first two parameters)
But normal presentation expected would be
Further the output outputs a linked language name, contributing to overlinking in the article. GraemeLeggett ( talk) 21:17, 16 January 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: Change from outputting "transcription" under native title to "transliteration" Diff:
− | + | "transliteration" |
GraemeLeggett ( talk) 21:06, 16 January 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change:
Per
Wikipedia:Manual_of_Style/Japan-related_articles#General_guidelines, referrring to
Wikipedia:Manual_of_Style#Foreign_terms transliterated text should be italicised, currently it is not. The display code needs to be changed to italicise the output from the | TranslitTitle =
parameter
Diff: So when applied to first episode listed at Full_Dive#Anime
Should render as
GraemeLeggett ( talk) 19:38, 17 January 2024 (UTC)
Deactivating edit request as weeks in there still seems to be no agreement on any specific change to be made. Please come to an agreement, code it in the sandbox, and, if you still need an uninvolved template editor to implement, reactivate the request. * Pppery * it has begun... 02:56, 6 February 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
When Guests and MusicalGuests were originally requested here, there was a requirement that they would be aliases of Aux1 and Aux2 and would not be able to be used at the same time, which is indicated by a comment in the code: Module:Episode_list#L-57. But in fact they freely coexist separately as independent parameters (also being undocumented):
aux1 | aux2 | aux3 | Guest(s) | Musical/entertainment guest(s) |
---|---|---|---|---|
Aux1 | Aux2 | Aux3 |
I still think it should be the way it was originally intended to be. That it is, they should be aliases for Aux1 Aux2, created simply to force predefined headings. Solidest ( talk) 12:43, 7 February 2024 (UTC)
Discussion at Talk:List of Hunter Street episodes about whether to include writers and directors, any thoughts please. Thanks, Indagate ( talk) 09:42, 12 March 2024 (UTC)
There seems to be some problem with this template. Short summaries are no longer visible. I'm assuming this isn't deliberate? Skteosk ( talk) 21:55, 30 March 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: The short summary section of this template does not appear to being showing up on any pages. I have checked multiple different TV shows on different browsers and the Wikipedia App. Zachary Sikes ( talk) 03:45, 31 March 2024 (UTC)
In cleaning out the mess I made with the whole episode move thing, and as an extension of
#Fault? above, could we get a tracking parameter set up for the /sublist template for when |1=
is provided but doesn't match the pagename?
Primefac (
talk)
08:50, 1 April 2024 (UTC)
|1=
parameter is "Attack on Titan season 1" (and because the page and parameter match, the episode summaries are shown), but when that episode table is transcluded to
List of Attack on Titan episodes, the |1=
parameter will still be "Attack on Titan season 1" (and because the page and parameter don't match, the episode summaries are hidden). --
Alex_21
TALK
09:07, 1 April 2024 (UTC)