User talk:FeRDNYC/Sandbox

From GodWiki
< User talk:FeRDNYC
Revision as of 09:35, 16 January 2019 by FeRDNYC (talk | contribs) (Switch to Template:H2 instead of Template:spacer)
Jump to: navigation, search


This page has an /Archive

Old and/or inactive discussions have been moved to the archive subpage.

Mobile App Template / Infobox Display

As Djonni suggested over on the Adminotaur talk page, I've had a look at these templates in the Godville Android app (6.9.2) and got these results. Device - Galaxy Core Prime (4.5" screen), Android 5.1.1. -- S624 (talk) 21:06, 8 January 2019 (UTC)

Many thanks! OK, those are the results I was both expecting and dreading. It means that the div.thumbinner is what's causing the infoboxes to be cut off (which I guess makes sense, as it's styled overflow:hidden). So at least I can get things to format merely "as badly" on your device as on the rest of ours, by simply removing it. (It still really is striking how much worse all of these format in the game browser, than they do in Firefox/Chrome on the same device. I know at least on mine, everything is perfectly centered and visible in any browser except the game browser.) -- FeRDNYC (talk) 03:01, 9 January 2019 (UTC)
Not a problem. The templates (here & in the wild now seem OK in the GV App on my device. The only issue I forgot to bring up before was the guild template. The infobox displays OK but cuts various bits of text / headers off in portrait mode (landscape mode OK). Examples -- S624 (talk) 19:58, 9 January 2019 (UTC)
Ah! Thanks, that {{Guild}} thing is really odd. But, I'm planning to re-do that template using {{Infobox}} anyway; I'll just accelerate my plans a little, since it's actively breaking stuff.
ARRRRGH! Crap, I also just noticed from your Beer goggles screenshot that the baseball-cap emoji (🧒) isn't showing up either. Well, I knew there would probably be some device that didn't support it, since it's one of the relatively-newer ones.
(Psst, hey Djonni, we found one!) Still, no huge disaster, just that slightly ugly-looking replacement character before "Head" in the "Worn" field. -- FeRDNYC (talk) 23:02, 9 January 2019 (UTC)
Ahhh dammit, I thought we'd caught all those! πŸ˜‚ What were our second choices for that? 🎩 (top hat introduced 2017) and 🀠 (coyboy hat introduced 2016)? --Djonni (talk) 10:57, 11 January 2019 (UTC)
Let's see, what did I write at the time...

Which means it's probably going to end up being the baseball cap 🧒, even though I was trying to avoid that after using both the t-shirt and jeans. But the top hat 🎩 is just too "much" (and too male), the woman's hat πŸ‘’ is just too "much" the other direction (and too female), and the crown πŸ‘‘ is way too painfully cliche. I suppose I could use this: 🀠 (It's certainly different.)

Emojipedia says the top hat was Unicode 6.0 (2010) / Emoji 1.0 (2015), while the cowboy hat was Unicode 9.0 / Emoji 3.0 (2016) β€” so cowboy hat is barely older than baseball cap and would likely have all the same problems. (Also, it's the head of the emoji sheriff so that's just plain ew.) And I still hate top hat for the same reasons as always. ...Honestly, at this point I'm sort of leaning towards, "leave it the way it is and hope S624 and all the other users of Android 4/5 devices eventually upgrade"? -- FeRDNYC (talk) 15:52, 11 January 2019 (UTC)
Seems like a bearable strategy to me ;) -- Djonni (talk) 16:03, 11 January 2019 (UTC)

Preliminary reimplementation of Template:Guild

There's now a preliminary version of the {{Infobox}} rebuild of {{Guild}} previewing at the bottom of the page. -- FeRDNYC (talk) 16:06, 10 January 2019 (UTC)

Testing - New version looks OK in the app & desktop but a bit iffy in mobile browser. -- S624 (talk) 18:37, 10 January 2019 (UTC)
That's odd... in Firefox portrait mode, you would've been able to swipe the page rightward to reach the rest of it to the left, though, yes? The page was formatted wider than the screen because there were other elements (embedded images) that forced its width, but I've never seen a problem where you couldn't "scroll" to make the entire area of the navbox visible, at least in Chrome (mobile). (I've only seen the app browser prevent that.)
Anyway, I removed all of those other samples so that the page won't format too-wide (though in truth that's a bad test, since many, many real articles do format too wide for mobile), and I also experimentally reduced the width of the navbox even more, which on my phone prevents the app browser from dangling it off the left edge of the screen (unreachably). -- FeRDNYC (talk) 07:07, 11 January 2019 (UTC)
I don't think I was able to swipe and see the rest of the infobox before you removed all the other test templates, I can now though. The archive template is also behaving oddly. Presumably this is to do with the content (or lack of) before the first header line? -- S624 (talk) 21:52, 11 January 2019 (UTC)
No, that's just the way web layout works when you have no control over the page CSS. There are plenty of things that could be done to mitigate those problems, but they all require stylesheet rules that aren't in place. Without them, that's what you get.
The devs have refused to make even small modifications to the CSS rules to fix bugs like the "Contents" header issue and the multi-column list formatting problem, so adding new CSS rules to enhance layout seems completely off the table. And unless someone with access to edit the site CSS is working on these layout issues, they're not going to be solved. -- FeRDNYC (talk) 07:37, 12 January 2019 (UTC)

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜CSS and mobile layout issues aside for a moment, that guild infobox looks really good. I was hoping you'd turn your gaze towards {{Guild}} and {{Hero}} next, and so far it's looking just fantastic! -- Djonni (talk) 13:59, 12 January 2019 (UTC)