Board Thread:Administrator's Noticeboard/@comment-171752-20150806153014/@comment-3157150-20151022081552

Anon1681 wrote: Dzylon here. What perceived issue are you actually looking to fix here? A couple pieces of information are obscured on mobile, so we need a couple of tweaks, but our infoboxes work pretty well on phones already. What use is there for any kind of serious restructure when you're already handling things with mobile-specific CSS?

http://i.imgur.com/N9ZvVoi.png

Edit: Btw Path, if you add alt codes to the images in the quality and coins templates, I think those bugs shown in the screenshot I posted will be fixed. Heya Dzylon, I'll test out the alt codes and try viewing them on my mobile browser, thanks for the tip! I would never have thought of it myself. Also, have you lost access to your previous account? CzechOut wrote: Hey Pathogen —

It would help us help you better if we knew precisely what loss of functionality you think might be on the cards. Do you have any examples of functionality that must be preserved for you to perceive of the mocks as successful? The way most of our infoboxes work is through multi-leveled template transclusion; my worry is that this functionality would be damaged or made more complicated/less efficient. Example: This being just one example, I wonder how the new code would affect this function. Also, I am of a mind with Anon1681 above (or as it seems), in that a couple of tweaks are all that I believe should be needed.
 * 1) Infobox:Item checks the validity of an item's value parameter to see if it's the proper numerical value (e.g. 12345 for
 * 2) *If it's a valid number, it'll use ValueCalc to display the correctly-formatted amount.
 * 3) *If it's not, it'll simply display whatever the value parameter was set to (e.g.  for   )