User talk:Sitb

From Spellbreak Wiki
Jump to: navigation, search

FandomMobile Formatting Issues[edit source]

According to This Page the new mobile layout is supposed to be opt-in, but in my testing it seems to be opt-out instead, and users who aren't signed in can't opt-out at all.

The new layout is not compatible with the sketchy formatting made specifically for the legacy mobile skin.

I would prefer In the short term, if possible, for FandomMobile to be disabled on this wiki, or at least properly opt-in as was intended.

In the long term, I recognize that all wikis will eventually have to use the FandomMobile layout. I'm willing to transition to using it, Spellbreak Wiki is not that large comparatively, so it should in principle not be a lot of work.

But try as I might, I simply can't get the tables to behave how I want them to. I would like some assistance specifically with Outfits & Talents to start with. All other tables on the site use roughly the same formatting as those two, so if those get fixed, I should be able to handle the rest. Thanks in advance. Skolander (talk) 23:19, 12 March 2021 (UTC)

Category Media Limit[edit source]

I would like the category page limit increased to 500, would be convenient for users who frequent the Category:Outfits page for an easier overview of current skins in the game.

To my knowledge, the code to add to the LocalSettings.php should be $wgCategoryPagingLimit = 500

Thanks. Skolander (talk) 01:03, 13 March 2021 (UTC)

Hi there,
I've been told that we can't do that, because it would involve changing something that would affect more than just this wiki, and that it's not optimal for the platform. Higher limits are also discouraged in general, since it can greatly increase page load times, resulting in a poorer user experience.
- Sitb 19:37, 16 March 2021 (UTC)

More FandomMobile Optimizations[edit source]

Thanks for the help with the tables, has made my formatting hell a lot easier.

I have another request however. It seems like whenever an image is rendered inside a table on mobile, it always takes up roughly 10 pixels more row space than it should, and the size of the image is always incredibly small. Thumb, frameless etc. don't help the issue, neither does setting padding to 0, so I'm not sure what else to try. Skolander (talk) 03:27, 14 March 2021 (UTC)

I've taken a look at a few pages with tables on my mobile device, but I can't seem to find any cases where there's notable "wasted space". Do you have a good link/example of a table that exhibits this behavior?
- Sitb 19:01, 16 March 2021 (UTC)
The Accolades Table for example. Here's an image of what I mean:
If it's not obvious on most tables, it is because I haven't brute-forced them to be their proper size to fill their cell yet. Skolander (talk) 19:35, 16 March 2021 (UTC)
I was speaking with a colleague and he mentioned that one possible way to minimize that wasted space, could be to add styling to MediaWiki:FandomMobile.css, removing the margin-bottom on images in tables (or tables with a certain class).
- Sitb 20:02, 16 March 2021 (UTC)
Interesting, hadn't thought of removing margin-bottom might fix it. Is it possible to add that to the "wikitable" class? All tables on the site already use that one. Would save me some time if it works. Skolander (talk) 20:12, 16 March 2021 (UTC)
You could try that if you'd like, but because this is a mobile-specific issue (ie. the extra margin space doesn't appear like that on desktop), I'm not sure if the mobile view would recognize that customization outside of MediaWiki:FandomMobile.css.
- Sitb 10:28, 17 March 2021 (UTC)
I've discovered that it apparently renders images wildly differently on mobile depending on the size of the image. If an image is 50x50px or below, it will render as a tiny roughly 20x20px image, and be inline. But if it's larger, it will render as the size specified, but then display the weird "wasted space" + line break behaviour. Is there any way to standardize this so it behaves more like on Desktop? Or at least just in a consistent manner regardless of size. It's quite a nightmare to work with. I can't be the only user who has this issue with the mobile skin? Skolander (talk) 05:44, 26 March 2021 (UTC)

I'm trying to think of a use-case where a table would need to use multiple sizes of images, rather than standardizing the size of all images to be placed into those table cells (if you have a good example of this on the wiki, please share). If we decide on a standard image size for use in tables, would that not solve any unanticipated variations in formatting from using images of multiple sizes?
- Sitb 12:45, 27 March 2021 (UTC)

The most Notable example I can think of is one where I have tooltip images inside a table, such as when I denote a price, or a mastery requirement, see Badges. So a per-cell solution would be best I think. But ideally I would want images to behave "normally" inside or outside tables. Skolander (talk) 13:07, 27 March 2021 (UTC)
Standardizing images to a smaller size that is optimized for tables would also have a beneficial side-effect of quicker page-load times for users who aren't connected at optimal speeds. So, I think that's something to consider as well.😉
- Sitb 13:16, 27 March 2021 (UTC)

Internal Link With Purge Functionality[edit source]

Is it possible to create an internal link with purge functionality that doesn't open in a new tab / window?

I'm building a Build Generator which outputs a random build on each refresh / cache purge.

So far all the link methods I have tried yielded in external link behaviour. Is it possible to overcome this limitation? Skolander (talk) 22:06, 6 April 2021 (UTC)

I'm not aware of a method in the standard/basic mediawiki environment that can accomplish this. I did look around for some information and even brought this question to my colleagues. One of them suggested this page might be talking about the problem you described (specifically, the part in the code that says "Avoid the purge confirmation all together, restoring legacy behaviour until extension is fixed").
Are you familiar with the DPL extension? Unfortunately I don't personally have experience with that extension myself, but I know there are a bunch of Fandom/Gamepedia users in the community discord's dpl-help channel who are. I'm not sure if you've ever visited that community information resource, but you may find the answers you're looking for through conversations with those DPL experts.
- Sitb 10:03, 7 April 2021 (UTC)
Thanks, I'll check it out! I will let you know if I need to install the extension.

FandomMobile Image Resizing / Flickering[edit source]

The images in my tables have started constantly resizing each time a new one loads in on mobile. As you scroll down the problem gets worse. It doesn't happen when viewing the mobile version on desktop if the window is fullscreen, so I think it has something to do with how the table expands itself. Since it's occuring on the most popular page on the site, Outfits, I hope it can be resolved. That particular table is fairly complex, but it even happens in simple tables like the Runes Table. Any advice? Here's a video of the issue Skolander (talk) 17:10, 20 April 2021 (UTC)

I see the same on my mobile device and unfortunately, that type of behavior is to be expected. Tables are known to display content awkwardly on mobile devices. The ultimate mobile-friendly solution would be to simply not use tables if you plan to display anything other then data (ie. images) within those cells. It is "best practices" advice that staff have tried to convey to wiki users for the past several years.

However that being said, since a lot of work has already been invested into those templates on this wiki, I believe in this specific situation you could greatly decrease the load times of the wiki's tables by ensuring the "...icon.png" images on the wiki are a more-appropriate icon size. The detail in a 256x256px image is lost when the image is shrunk down to be used in a table, whether you're viewing on desktop or mobile. So each time the table is opened, the visitor is forced to unnecessarily download hundreds of images in the table at once, at about 4-times the dimensions/filesize they need to be. Ideally to ensure tables load as smoothly as possible, they should primarily display information and if the user wants to see an image in proper detail, they can click on a link to view that elsewhere.
- Sitb 18:29, 20 April 2021 (UTC)
It's an unreasonable request to not have images in tables. Literally every noteworthy wiki out there puts images in their tables. We're not in 1990s anymore. What kind of response is this? Sure, I understand it happening in a table with 100s of images, but even with 5, it happens. Surely this is fixable, somehow. I can't imagine it happens to all the other wikis that have images in their tables. Skolander (talk) 18:39, 20 April 2021 (UTC)
It's certainly possible to have images in a table and still have those load at in a decent manner on mobile. It just possibly involves some different design. Here's an example of a wiki page where a table with images loads decently on mobile (they also use smaller icons).
- Sitb 23:47, 20 April 2021 (UTC)
Well, I luckily did find a solution! Thought I would share it. It turns out (unsurprisingly) that it's not just images less than 50 pixels than render wrong, larger than 50 do as well. You'd think setting an image to be 60 pixels would render it at said 60x60 pixels, but nope, it renders at roughly 90x90 instead, so you just need to define a large enough cell width to solve the problem. Now ya know, spread the word, I'm sure plenty of other editors have similar problems as me. Skolander (talk) 19:33, 21 April 2021 (UTC)

Extension Request[edit source]

I'd like the OpenGraphMeta Extension installed.

If I understand how it works correctly, it will allow me to choose which embedded image gets chosen alongside links shared on Facebook / Discord. Skolander (talk) 17:30, 26 April 2021 (UTC)

Not a problem! The extension is enabled. 🙂
- Sitb 00:49, 27 April 2021 (UTC)