« SMF bug: replying to topic with mismatch of replies
Weaving & Warm issues in iOS
Header headache »

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re : Weaving & Warm issues in iOS
« Reply #15, on January 24th, 2013, 06:04 AM »
Ok, this huge size isn't a quirk just for Retina iPads. I will screencap it later though, time for bed now.
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

godboko71

  • Fence accomplished!
  • Hello
  • Posts: 361
Re : Weaving & Warm issues in iOS
« Reply #16, on January 24th, 2013, 07:57 AM »
This is what warm looks like on an ipad 2 chrome browser
Posted: January 24th, 2013, 07:53 AM

Here is what warm looks like not logged in.

📎 image.jpg - 206.52 kB, 1024x768, viewed 265 times.

📎 image.jpg - 188.14 kB, 1024x768, viewed 249 times.

📎 image.jpg - 193.93 kB, 1024x768, viewed 248 times.

Thank you,
Boko

Nao

  • Dadman with a boy
  • Posts: 16,082
Re : Weaving & Warm issues in iOS
« Reply #17, on January 24th, 2013, 10:12 AM »
Quote from Aaron Smith on January 24th, 2013, 01:00 AM
The linktree for Warm looks nice, but the linktree in Wuthering is just straight sexy.
It is, innit? :)
Basically, each of my skins are my attempts at going in different directions, with Weaving being a crowd-pleaser and Wuthering the fanciest of all. Warm tries to be more 'modern' but I spent a long time ignoring it because it disappointed me on that side of things.
Now, again, the Wuthering linktree is something I love dearly (spent a LOT of time getting it right!), but I'm not sure that most skins would have it 'that way'.
Then again, it's probably just a matter of having the same, but instead remove box-shadows by default.

Re: iPad, okay, I finally was able to reproduce... Ready? It shows the same way in SAFARI WINDOWS. Lol.

But the oddest thing is, I think most of these strange font sizes make it look cooler, like... Well, a modern website :P But I'm not sure it's very good for a forum, with lots of content etc.
Re : Weaving & Warm issues in iOS
« Reply #19, on January 24th, 2013, 10:21 AM »
Okay, this is due to the fact that Wedge always forgets to record the OS name in the filename...
Although I'm not sure it would fix anything, because from the start, iPad and iPhone stylesheets have been the same...?
Re: Re : Weaving & Warm issues in iOS
« Reply #20, on January 24th, 2013, 03:09 PM »
Quote from Nao on January 24th, 2013, 10:21 AM
Okay, this is due to the fact that Wedge always forgets to record the OS name in the filename...
Fixed locally. This was a silly one... Can't believe I overlooked it.

Still don't know if it'll fix the iPod vs iPad problem, though... I don't think it will.
Technically, I think it never showed up before because (probably) the iPad was recorded as 'tablet', which was different from 'iphone', in the browser string.
Perhaps I'll have to do something about the 'ios' string, I don't know. Or simply add a dummy 'ipad' tag to the filename in case we're on an iPad. But it feels wrong to do that...
Re: Weaving & Warm issues in iOS
« Reply #21, on January 25th, 2013, 11:04 AM »
So at this point the site is up to date and works fine in Safari for Windows...

I just launched it on my iPod (iOS 5.1 - Chrome 23), at the very least try it on your iPads and tell me the results, and whether or not you're using Safari Mobile (which version) or Chrome (which version). Since both rendering engines are the same, the results should be identical too, except if you're on iOS 5.1 and using that version of Chrome, which is where it could get interesting.

Hack away!

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Weaving & Warm issues in iOS
« Reply #23, on January 25th, 2013, 12:05 PM »
Well.. Here's what's happening:
- Before, a long time ago, I'm guessing that the browser name was recorded as 'tablet' for iPads. I'm not 100% sure about that... But it's the only logical explanation to it failing now.
- Because now they're recorded as ios, it means they're sharing the same file as iPhones, with a larger font to accomodate for their ridiculous screen size. iPads are 'regular' tools for browsing, so they don't need the extra stuff. I should remove the 'ios' code for it. And/or restore the iphone/tablet difference I had before.

My main problem is that I don't have an iPad at all... :^^;: Hard to test in these conditions!

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278

godboko71

  • Fence accomplished!
  • Hello
  • Posts: 361

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Weaving & Warm issues in iOS
« Reply #26, on January 25th, 2013, 03:23 PM »
Not unexpected...
Technically it's all like I said... Before yesterday, there was a Safari header shared for all platforms. Now there's a Safari header just between iOS devices. It's still not enough, apparently.

So, yes, I could add a variable again... But what is it about, really? It's about element sizing. And what is the difference between iPhones and iPads..? Stuff that can be seen through CSS.
So the solution is to use a media query *even* when ios is already determined.
I'll look into that one... I've never used the DPI-specific ones. (Only pixel-specific. Although it could be enough, as the iPad resolutions are always > 960x640 anyway...).
Re: Weaving & Warm issues in iOS
« Reply #27, on January 25th, 2013, 04:11 PM »
Can someone test this site under an iPad now...?
I've added a minor change to ensure iPads don't change the main font size.


Please tell me if it works for you!

godboko71

  • Fence accomplished!
  • Hello
  • Posts: 361

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Weaving & Warm issues in iOS
« Reply #29, on January 26th, 2013, 07:22 PM »
Yep... Looking good I can see :)

BTW I'm at a loss about something... My code indicates that up until now, iPads were considered as wireless devices, and thus guests would get the Wireless skin by default. Can you confirm it's the case? Because your screenshots as a guest said otherwise, but OTOH they seem to be taken after specifically switching to that skin...
« SMF bug: replying to topic with mismatch of replies
Header headache »