Board Thread:Wiki discussions and announcements/@comment-3308937-20141123005532/@comment-11842624-20141127133758

Update
http://leagueoflegends.wikia.com/wiki/User:Hedgeg/Hecarim_in_tab_view?oldid=2160226 / http://leagueoflegends.wikia.com/wiki/User:Hedgeg/wikia.css?oldid=2159902
 * 100% identitial with Template:C-top
 * add rail with diffrent variants of additional links

Issues
(every single hand-made script doesnt work properly)
 * Template:Champion_info
 * Template:Sm2
 * User_blog:Emptylord/Background_images_on_Champion_pages

Additional text looks not great (it also creates unnecessary links in the mobile skin http://leagueoflegends.wikia.com/wiki/User:Hedgeg/Hecarim_in_tab_view?oldid=2160226&useskin=wikiamobile). I plan to completely replace the text with images. just need to find suitable images for comments and visual editor. Can someone help with that?
 * video preview of skills do not play ("WE all DIE!") .A real serious problem, because the rules of the video display and Tabview not be set up easily . see what Special:Contact/bug will tell us.
 * for overlay panels at each other, you must use absolute positioning. this makes impossible to correct the calculation of the indentation using CSS (you can see how the elements move out, if the width of the main content greater than 1024 pixels). so it requires a script for calculations.

Comments
as soon as there appears the script, which allow to load content from another page, this request will be solved. but most likely it will allow read only, not create your own comment. (such issues like interface improve must be solved by wikia-dev)

~Offtop
BlackSmith wrote: Hedgeg wrote: Secondly, you are not right. the table view does not affect the categories on separate pages. Really? Then it is just a glitch in my wiki instance that every article in e.g. Category:Champion_backgrounds has a '/Background' suffix. Are you trolling me? (Well, now i don't even want to talk with you.) This way of storing information. Distribution of information on articles. A common practice.
 * Tabview of course requires some time spent on calculations of the properties and rendering. you can compare the download speed is and  tab view. but these calculations are necessary, we cant escape this. By the way, someone can write a special script that loads the contents of the collapsed items only when necessary (the only disadvantage of this solution, the content will not be displayed in the mobile skin/ although in some cases, as  for example, it is rather a plus).

Jens Ingels wrote: If I was you I wouldn't implement the tabview. Whe all known wikia is already developing a new tabsystem.This system might solve the current limitations that are now available in tabview & others. Proofs?

Jens Ingels wrote: Btw the mobile version isn't that supportive on the new infobox: here. It is not so. as a user receives the information. (btw, this is offtop)

Mylittlewut wrote: Also I find this something to deteriorate new editors from editing cause sometimes they don't realize they have to go to another page/template away from the actual page to edit and it becomes mighty confusing for them (it did for me when i saw a tabber similar to this.) this can only help competently and correctly placed guide for new users (the problem with commenting in the wrong place and the inability to attach forum topics for articles to create discussions are solved in the same way)
 * on my part, I can only offer additional menu with links // by the way. almost every pattern that I have seen contains links to edit himself.