4/6/2023 0 Comments Tabber fandom![]() I've also migrated the Tavern Trouble 2021 Event ( diff) and Homer ( diff) pages manually to have an example of how things will look in practice.įeedback and ideas are welcome. I have several examples of the new custom tabbers on my sandbox where you can play with them (remember you need to be on the desktop skin in order for them to work). I've intentionally removed this since I think it is more confusing than helpful and always was just a workaround for having too long tab names in the first place. The new custom tabbers no longer support the ability to specify an alternative abbreviated title for the tab headers. Overall the new custom tabbers better in all except one point. NB: To use Oasis users already need to change the skin in their preferences and it will be completely removed in the future.Īutomatically displays and shows the tab belonging to the entry in the table of contents.ĭoes (intentionally) not support the alternative text from the old custom tabbers. However, it does not support the old Oasis skin whatsoever. Uses the same styles as the default tabber and therefor looks identical. However this makes it easier to edit the content. The only place where it doesn't display as tabber is within the visual editor. Works in the preview of all editors again. Supports the ability to add an alternative text that is displayed on the tab title instead of the text displayed in the heading in the table of contents. Probably does not work very well with multiple nested tabbers (but we never used that so far). The tab belonging to the selected entry in the table of contents will however not become visible, making this feature confusing. Produces entries in the table of contents that when clicked scroll to the position of the tab on the page. Has proper fallback on mobile, showing sections with headings for each tab. Try to mimic the look of builtin tabbers on the Oasis skin, but looks out of place in FandomDesktop and does not adapt to the dark theme at all. Editor preview is effectively broken at the moment. Only worked in the preview for one of the editors that no longer exists. Does not have the ability to tab displayed by default. Properly match the skin and theme of the page they are displayed on.ĭo not produce entries in the table of contents.Īlways displays the first tab when loading the page. Here is the feature comparison of the three tabber types: Namely they now work properly in all editor previews and clicking on an entry in the table of contents now correctly shows the tab belonging to that entry (previously it would scroll the page to the tab, not not actually make the tab visible). The new implementation now also fixes some of the bugs/bad behaviors of the old custom tabbers. Instead of being completely separate from the built-in tabbers, it uses their styles and some of their JavaScipt to resemble them more closely and reduce the amount of custom code. Instead of taking the old custom implementation and adjusting it to match the style of the built-in tabbers, I went ahead and created a new, second custom tabber implementation. It also was not prepared for a dark theme (which now exists in the new skin) and produces bad color contrast there. With the introduction of FandomDesktop the custom implementation now looks very out of place since the default styles have changed a lot. it will just display the sections with their headings normally. Therefor, it will fall back nicely when JavaScipt is disabled, i.e. The custom tabber is built based on headings and article section present on the page. For this reason I've introduced a custom tabber implemetnation years ago. This means getting a better fallback if JavaScript is not running, is pretty important. The normal tabbers provided by FANDOM have a bad fallback for mobile devices that makes it unclear what the different tabs are referring to.īeing about a mobile game, not surprisingly 75% of all page views for this wiki happen on mobile. However, FANDOM has disabled nearly all JavaScript on the skin used for mobile devices. Tabbers require JavaScript to be running in order to function. On the TSTO wiki we've had a custom implementation for Tabbers. If you only visit from mobile devices, this probably won't affect you. If you are using a desktop device to access the wiki you probably noticed this since it is significantly different from the old skin called "Oasis". Recently FANDOM migrated wikis to a new default skin named " FandomDesktop". Explanation/reasoning and feature comparison below. TLDR: I've made a new custom implemenation for tabbers that more closely resembles the default tabbers coming with the new FandomDesktop skin and intend to migrate all the existing tabbers to using the new version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |