That’s all. Doing that will make sure the Tournaments will keep working after we delete the old file (if you still want the Tournament iFrames that is, if you don’t want to bother with them you can ditch the whole import).
Ah yes I was just about to tell you. FANDOM Staff have been talking with me about it, & they need to have a meeting regarding whether iFrames (the thing the JS is using) should be allowed in general. If they decide it should be allowed, they will restore the import. If they decide it should not be allowed, then no more Challonge embeds :(
No No Noooooooooooooooooooooooooooooooooooo!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!...................Ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха-ха Я выиграл
Hey there. You may want to talk to AC0xRPFS001 about the tables he has been replacing the Infoboxes with. Tables are not good for mobile, so viewing it on your phone is going to be dicey. Portable Infoboxes on the other hand, show up very well in both Mobile & the main desktop skin, so if you want to make sure people can read this Wikia well on mobile, you might want to abandon the tables as replacements to Portable Infoboxes.
Actually we want to use some CSS trick to control when users use mobile, and the page won't show TankTable for them. When users use computer is similar to mobile. And Zollo told me about "display: none" and "class=hidden" to do that.
(code in display:none won't be showed on computer, and class=hidden won't be showed on mobile, he said)
In fact, class=hidden seems that it didn't do anything @@
Yes, I saw what was attempted. However, it is very hard to pull off because you are not meant to do it that way. Wide tables for design is a bad practice, & having a separate experience for Mobile & Desktop is an even worse practice. You want consistency across platforms, not a different one, especially since the upkeep of Infoboxes may be ignored since many editors cannot see it.
You can display all the data you want to display in an Infobox, it is possible (see 使用說明:訊息框), but using the table route (or having different items in desktop & mobile) is going to produce a worse experience for Mobile users.
Looking on my phone I still see that table. ?useskin=mercury is not actual Mercury, it’s like a pseudo-version of Mercury.
Now, I have a question: why do you guys want to use a table so much? There is a better way to ensure that the table does not show up in Mercury (that isn’t as buggy as class="hidden") that I can show you if you are absolutely certain you want to use that table in desktop, but I assure you that an Infobox is considerably better & I would like to try to change your mind.
Do you know about web-readers? For blind people? Or the preview text that is displayed on certain websites like Discord when you link to a page? Infoboxes are ideal for those things, but what you effectively have here is the same data twice, just one is hidden on different skins due to CSS. That CSS doesn’t matter to web readers or to embedded previews, so outside this website you can end up with the same information repeated twice / web readers may read the same things twice. Even worse, since tables aren’t optimized for web readers, the result is that they’ll hear it correctly the first time & then hear it incorrectly a second time; that’s really confusing right?
There’s a lot of reasons why you do not want to have one thing on desktop & another thing on Mobile, & that’s why I want to discourage you from using these tables at all. It is possible to fit all of the information you have in that table into an infobox, only now it will span vertically instead of horizontally, & that forces you to write more textual content on the left to keep up with increased length. This provides a better experience for readers & keeps them hooked, whereas now they may just read your table & then leave.
Also, look at this:
The last issue with these tables is SEO. Search Engines like to take the “top” text of an article (the intro text before any headers) & use that for queries. If that text is gone, e.g. the table has replaced it, then Search Engines like Google have a harder time finding your content & therefore, so do your readers have a harder time finding your pages here. It won’t happen immediately, Search Engines have a lot of caching, but eventually it may harm the views you receive. Portable Infoboxes on the other hand, do not disrupt that.
(Also, like I said earlier about it basically being duplicate data? The same data twice? Google & other search engines like to ignore content that has been copied verbatim, so by having it twice you are teaching Google to ignore that data on your page & so it fails to help your pages get views, whereas with just Infoboxes that doesn’t happen).Do you understand all of the secondary benefits to not using tables for desktop & Infoboxes for mobile?
@Ursuul Okay I got it. I'll tell Zollo (or maybe he will look these himself). After I read you comment I know table is a really not good idea. Maybe we'll give up soon (if Zollo want). We didn't think about this (or should I say "these"?) before. Thanks for reminding.
But I still curios about how to no show up table in Mercury :P
Ah thanks. I believe I have a pretty good idea of how to both display all the same data as your table while also styling it to make it look similar to your table, just vertically instead of horizontally. Once I have the template doctored then I will write CSS for it, & finally I will show you the end result :)
I am done. Here is an example, although you really should copy this CSS into this page to be able to see what it would look like. It appears like this:
You cannot see the whole thing in the image because it is fairly long, you’d have to visit the page itself. I can decrease the padding to make it shorter if you want though, if you think it’s too long.
That would not happen. MediaWiki:Common.css only effects two skins: the Oasis skin (the default desktop skin you see now) & the Monobookskin which you can choose in 特殊:參數設置. MediaWiki:Wikia.css on the other hand, just does the Oasis skin & MediaWiki:Monobook.css just does the Monobook skin. It is good practice to have MediaWiki:Common.css totally empty, so that you can use CSS imports in Wikia.css/Monobook.css without bugs (although if you want to use a single file for both skins I can show you a best practice way to set it up).
The skin mobile users see is called Mercury; it is not effected by any CSS or JS files at all. However, the simple fact that you are using an Infobox instead of a table will make it look a lot better & cleaner on your phone than a table would be though.
I think the gray appearance has the better one, if I want to make all Desktop users see the gray one, how should I do? Put them into MediaWiki:Themes.css? (because you said I should better keep MediaWiki:Common.css empty)