Usage
Parameters:
- : type of move
- : generation move was introduced (optional - defaults to one, should still work as normal even for other generations if not set)
Any changes needed or questions, feel free to ask here. Werdnae (talk) 06:40, 25 May 2011 (UTC)
Colspan
I've noticed on several pages — I saw Land's Wrath just now, and I'll come back and point out any more that I notice — it seems that the Movefoot template is spanning one more column than it should, leaving an ugly fringe to the right of every row except the move footer. Is this a problem with the template itself, or with the pages that are calling it? If the former, can it be fixed please? If the latter, can someone please explain to me how to fix it, so I don't have to ask for help if I notice it on more pages? Pumpkinking0192 (talk) 06:28, 20 December 2016 (UTC)
- Actually, I just consulted a small semi-random sampling of move pages — Core Enforcer, Tackle, Hurricane, Mega Punch, Flatter, and Shadow Force, in case anyone cares — and it's been true for all of them, leading me to believe it may be true for every table this template is used in. I suppose that means the problem is with the template, then, rather than its execution on individual pages. Pumpkinking0192 (talk) 06:34, 20 December 2016 (UTC)
- I don't see any problem in Firefox or IE. Tiddlywinks (talk) 06:55, 20 December 2016 (UTC)
- This is what I'm seeing. I use Chrome. Pumpkinking0192 (talk) 06:59, 20 December 2016 (UTC)
- Yeah, this is an issue with colspan. Since the footer doesn't care how many columns there are, it just uses an excessive colspan. That looks fine on Firefox, but you get that bit of overshoot on Chrome. This has come up when designing templates before. The ideal solution would be to allow the footer to have the number of columns specified so it can span the appropriate number. --SnorlaxMonster 09:17, 20 December 2016 (UTC)
- Should someone do that, then? Pumpkinking0192 (talk) 16:20, 20 December 2016 (UTC)
- Actually, it looks like it's already there. It looks like you're supposed to just enter the generation the move was introduced (i.e. the same number as in the header), but for some reason it seems to be assuming each generation has two columns rather than one, so it doesn't work properly. I'll make sure that gets fixed at a low traffic time. --SnorlaxMonster 16:31, 20 December 2016 (UTC)
- Thank you! Pumpkinking0192 (talk) 16:40, 20 December 2016 (UTC)
- Actually, it looks like it's already there. It looks like you're supposed to just enter the generation the move was introduced (i.e. the same number as in the header), but for some reason it seems to be assuming each generation has two columns rather than one, so it doesn't work properly. I'll make sure that gets fixed at a low traffic time. --SnorlaxMonster 16:31, 20 December 2016 (UTC)
- Should someone do that, then? Pumpkinking0192 (talk) 16:20, 20 December 2016 (UTC)
- Yeah, this is an issue with colspan. Since the footer doesn't care how many columns there are, it just uses an excessive colspan. That looks fine on Firefox, but you get that bit of overshoot on Chrome. This has come up when designing templates before. The ideal solution would be to allow the footer to have the number of columns specified so it can span the appropriate number. --SnorlaxMonster 09:17, 20 December 2016 (UTC)
- This is what I'm seeing. I use Chrome. Pumpkinking0192 (talk) 06:59, 20 December 2016 (UTC)
- I don't see any problem in Firefox or IE. Tiddlywinks (talk) 06:55, 20 December 2016 (UTC)
Looks great now! Thank you so much for all your hard work, Kogoro and Carmenstar! Pumpkinking0192 (talk) 17:40, 23 December 2016 (UTC)