Board Thread:Support Requests - Getting Technical/@comment-28659120-20161230235733/@comment-26402117-20161231175047

Ah, I see. If you want to have level-based data, you can:


 * use the tabbers as you have. Mobile users will see three separate infoboxes.
 * have one combined infobox with each data in horizontal grouping

The HTML inline styling doesn't work with anything inside the tag, as it breaks portability's core concept of splitting up content from the presentation.

This split gives the mobile skin and search engines info on what the layout of the infobox is, simply through the code - they would struggle otherwise. It also lets you change things, like the color scheme across the wiki's infoboxes, from the wiki's stylesheets.

I was going to look into it, but I see that TableWiz gives a good code-based solution. I can suggest changing the table on the outside into a  tag and moving the inline styling to the stylesheet. The SN image tabber is broken in Mercury, so you may want to change the tag from a "data" tag to an "image" one.

.Carte { width: 320px; background: #012647; border: 2px solid black; float: right; margin: 0 auto; padding: 2px 5px; text-align: center; }

If you want someone to help you with further improvements to the infobox and CSS, I can do so - with permission and much sandboxing beforehand. :)