Final Fantasy Wiki
Final Fantasy Wiki
Gilgamesh: Enough expository banter!
This talk page is used for discussing improvements to the page "Foot". It is not the place for general discussion or sharing stories about the topic of this article.

This doesn't have the underline thing in Oasis. So it's just an asterisk with no indication you need to hover your mouse over it to reveal the message. 13:37, October 24, 2010 (UTC)

Ubuntu Linux[]

Not sure if it's my OS, but it looks odd. It displays it twice.

I wouldn't be surprised if this hadn't been reported before, as so few people use Linux and as it's such a small issue. But it's there.--Magicite-ffvi-ios.png Technobliterator TC 12:44, June 20, 2014 (UTC)

You are one of only a few people that see it. ?tester=false. It was a just a test to demonstrate that we can use a HTML pop-up instead of a title attribute for foot. This would allow things like images and links to be shown too.
No forum was started for the matter because... things to do. 16:50, June 20, 2014 (UTC)

Param specifying[]

Got bored. So I added in a few parsers and alternative params. Basically, as I said on the template's doc; Additionally, parameters can be specified as text or tip. For instance, {{subst:Foot|text=text1|tip=text2}} will produce the same results. People okay with this?--Magicite-ffvi-ios.png Technobliterator TC 14:58, July 9, 2014 (UTC)

It is also possible to add links of additional styling. Typing text1 (text2) will produce a similar result. To use styles, a style parameter must be specified, and it will specify the text displayed on the page, not the text displayed in the tooltip when hovering over the mouse. text1 (text2), for instance, will produce the same result, except the text will be red.
That alright? If not, it can be reverted.--Magicite-ffvi-ios.png Technobliterator TC 15:08, July 9, 2014 (UTC)
Yeah, the additional parameters are kinda pointless. Why can't you just wrap the foot in a link or span tag? Also having the link as a nameless parameter is also a bad idea.
Naming the optional unnamed parameter is not a bad idea though, though "text" is pretty unexplanatory, and only makes sense when contrasted with the other parameter name. 18:20, July 9, 2014 (UTC)

Mobile footnotes[]

This template is dependent on JS, which is not functional for mobile, resulting in this effect. Of course, everything dependent on JS is broken, but for this I can't just copy-paste the appropriate lines into Wikiamobile.js because you can't really mouseover on a mobile phone. So we got a couple of options for mobile

  • Just remove the footnote text altogether
  • Shrink the text down to a smaller font size
  • Put parentheses around the footnote and give it a separate line

or whatever. pls discuss, I'm not sure the best way to handle this. C A T U S E 04:55, August 4, 2015 (UTC)

[02:49] <JBed> i want to at least add an X to the top-right of pop-ups, and have clicking on the thing that brings up the foot keep the footnote permanently there until Xd. but then i'd have to rewrite other stuff. i don't know about mobile development
I guess that would be a solution. Clicking on the footnote. This does result in a problem like this (>:(). You'd have to click the dotted underline without also clicking the text (Edit: Oh, looks like that's not how it currently works. Another thing to investigate).
The obvious solution for that is to add an icon to the end of foot indicating there is mouse action, but in the above scenario that icon would still be inside the <a>.
Another solution could be that when there is a footnote on screen, something pops-up that can be tapped to reveal show all on-screen footnotes. That idea might need some work.
I normally wouldn't advise putting a foot with a link anyway. I've still done it for images before, like on Chaos Elgo where sprite size exceeds 250px though. JBed (talk) 01:56, August 6, 2015 (UTC)
OH! I just realised what I was looking at in that screenshot. So the fact that you're seeing that Japanese text, the thing that's in the footnote there, is not by anyone's design.
To get the footnote's to work we need to embed the text to the page. And we need the wikitext/HTML to render as HTML so we need to put it an an unseen element. That element gets displayed:none. But on the mobile skin, when the wikitext gets rendered it removes display:none from the CSS.
The JavaScript comes in and sweeps away those display:noned elements so you don't see them on the mobile skin with working JS. Unless you look before the JS runs.
The fix to this is rather simple. Move JavaScript handling of foots over to verbatim-JS, which is what I want to do anyway. It means we don't have to wait for the page to load to hide that text. JS loaded in that verbatim should also run unless Wikia's JS is the thing preventing JS load on your mobile. And if JS is turned off we can have people see what you see in that screenshot on all browsers, though people with JS turned off will be in the minority we simply have pity for. JBed (talk) 03:35, August 6, 2015 (UTC)


The block tag inside the inline tag was screwing with wikitext parsing. On my userpage anyway. My use of lists and shit may have screwed around with things. But instances of foot were closing an extra element each time, so a few instances in the closing tag for article content had occurred.

I'm not sure if it will have a knock-on effect. There are probably some cases where we'll want to use block elements inside the pop-up, so I don't know if that would end up causing similar problems. I also don't know whether the tag I changed exists when the JavaScript is finished or if its only its contents that the script takes into account. JBed (talk) 00:48, May 30, 2016 (UTC)

Mobile display and display:none[]

So I added brackets that are only meant to appear on mobile. And if you go to the edit form of this template and click Mobile preview you'll see it works. As the WikiaMobile skin ignores most CSS, setting display:none to an element has it display:none on desktop but not on mobile.

But when I went to look at it on an actual page, I found something strange. Vivi Ornitier/Brave Exvius if it's used in a PI, display:none works. In fact, all the usual CSS works. (There must be a way to abuse this...)

But the solution to this is simple, we create a CSS class called something like hiddenStructure and set its only value to display:none. Because mobile doesn't have access to our stylesheets. Unless there's an official way to have something display on mobile but not desktop. JBed (talk) 03:44, July 13, 2018 (UTC)