So, here we are in a hotel room with decent wifi and we thought we'd check out the sidebar.
Your non-wifi connection seems decent enough, with Louis posting daily video updates on the road..
;)(I must say, it's interesting that I was finally able to see you 'live' after 3 years working together and only knowing you from a single picture, and yet you're 20 times further away from me than you usually are...
:^^;:)
We have an iPad 2 and an iPad 3 (so, one 1024x768 and one 2048x1536 retina display) both running Safari with iOS 6.1.3, neither has been modified or running dev code at this time.
Okay, my setup is (still) as such (I feel I need to make it clear that I can't test everywhere):
- Windows 7, main dev browser has been Chrome Canary for 6+ months, usual test browsers are Opera 15, IE10, and sometimes Firefox Aurora. These days, also Opera 12.16 (cf. comments in the thoughts.)
- S3 smartphone with Android 4.1.2, rooted, using the regular Chrome, with Firefox Beta as my occasional test browser, and very rarely, the stock browser (which I think sucks.)
- iPod 4 with iOS 5.1.x (probably just 5.1), rooted, using the regular Chrome. The only reason I've re-charged it these days, is to play Ron Gilbert's Scurvy Scallywags (very nice game, albeit a bit hard, so reliant on (bad) luck that it can get troublesome...), and Safari used to crash on me, but apparently, these days it doesn't, so I just tried on it...
It looks like the current Safari + iPod version gives me a different result... Instead of having the fixed button on the top right, it shows it on the top left (?!), and only a very small portion of the button, uh... Yeah, sure, great devs at Apple...
Here's where it gets funky. On the iPad 3 (retina one), I don't see a sidebar displayed, even in landscape. It's hidden and I have to unhide it, which is fine.
Hmm, I think it should have shown it...
You definitely should try remote debugging Wedge from your Mac. You have a Mac, I believe..? Since I don't, and don't plan to ever buy one, I can't debug their stupid Safari, and thus, can't see which media queries are triggered, etc...
The media queries are as such, IIRC ($response = max-width: 1000px):
- "$responsive" hides the sidebar, and shows the sidebar button in the top_bar, where it sits next to the Upshrink icon and Search form.
- "$responsive and min-resolution: 1.5dppx" additionally makes the sidebar button a fixed button, and moves it to the top right corner.
And, that's all there is to it...
The first query should run everywhere (including iPads), if the windows is shrunk. The second query specifically targets smartphones, by ensuring we're both in a low res, AND we have a Retina screen or better. Of course, I could simply test against the OS, or the 'mobile' variable, or both, as it would thus take bad screens into account... But, well. I'm not sure about this.
Normally, an iPad 2 shouldn't trigger the second query, but an iPad 3 and iPhone/iPod 4+ should. As I said, my iPod 4 doesn't show the button entirely, but that's probably down to a change I made yesterday, which I'm bound to cancel at some point, i.e. I changed the button width to use vw units (percentile of viewport width), which is great, but messes up the button in desktop mode, ah ah... (I even had to add an @if mobile test, to ensure it wouldn't screw up.)
The iPad 2 on the other hand, shows the sidebar all the time, even in portrait mode, even after refreshing the page.
It shouldn't... So, Apple is giving you the complete opposite of what normal browsers would give you. Try Chrome for iPad, will you..? I'm sure it'll magically start working, then...
Also, I assume the sidebar button is positioned at the top of the viewport when going to a page? I don't entirely know what is intended but here's what I'm seeing on iPad 3: the button appears at the top of the page for wherever I go to. So for this page for example, I came here from other navigation and arrived at #new, so looking at the last post and the sidebar button is aligned with the last post.
Hmm yes.
Now, aligning it with the top of the page when the user lands somewhere is neat - provided it follows them. Otherwise they could easily jump to the mid point of a page and then not be able to find the sidebar again because the button is somewhere on the page. Now, if it is supposed to follow my movements, it's not doing that.
Then, it's another Safari bug.
iOS didn't support position: fixed at all, years ago, but now it's supposed to... In fact, it does support it on my iPod+Safari, if you don't take the button size into account.
I did, while writing a long post, see the sidebar button manifest itself on the far right of the page just above the quick reply area, but only for a short while before it disappeared to who knows where - I was writing a long post and didn't see where it went.
It shouldn't happen.
Wait, if I'm in the editor and delete a line of text, such that I force the content to come back down to me (e.g. long post, I double-hit enter to make new lines then delete those lines) the button will appear on the far right of the page but will move if I cause the editor to scroll in any direction.
Is iOS 7 out, already..? I'm sure they'll do something for Safari, won't they..?
It's interesting but it seems unreliable to me :( (it's a shame because I can see how hard you've worked but I keep finding things that cause it to break)
It should work much better than before really; reason being, the new implementation is a different philosophy. Instead of doing plenty of changes, it simply hides the sidebar, and then it relies on JavaScript to show the sidebar again, and do the nice animation, when clicking the sidebar button...
:-/So, I'm definitely not going to give up on this, but I'm guessing I'll have to rely on someone with a Mac to do the debugging for me, because I'm not buying a friggin' Apple computer just for the sake of ensuring they didn't screw up with my code, eh...