Yeah. We're adding this to the FAQ right now, but the updates are free for the life of the theme (including updates to future versions of Bootstrap) <3

I totally agree. Been thinking about the best way to handle this and will have something in the near near future. Promise.

This is awesome! Browser chart more than just a quick list might be nice. Adding it as an outstanding issue to my long list of improvements. Appreciate the feedback!

You're welcome. Based on my testing, I think you don't even really need a detailed chart, just a compatibility list. You'd be safe listing it as compatible with:

Mozilla Firefox (desktop and mobile)

Google Chrome (desktop and mobile)

Chromium

Internet Explorer 9 and later

Opera (desktop and mobile)

Safari (desktop and mobile) [this is an almost-positive guess but test to be sure]

You could then work backwards a bit on version numbering, trying older versions until you see where it breaks. You could put Firefox 31+ for now (since I tested 31 ESR), but that would be misleading since I'd wager it works quite a ways back on Firefox. Same with Chrome, Opera, and Safari. You could even just leave those versions off as users generally have the latest version of Firefox, Chrome, and Opera. Safari is another story since it's OS-tied like IE is, so you have a lot more users using an outdated version of desktop Mac OS X's Safari than outdated Firefox or Chrome users on the same OS versions. Leopard users are stuck on Safari 5.0.6 and Lion users are stuck on Safari 6.1. If you can get your hands on really just those two versions to double check, you'd be set and could list it as Safari 5+.

I may test back a bit as I'm playing with using Skeleton for an older site using Drupal with a single-page theme. I can drop you a note if I do.

I don't believe it is, but maybe I should go about getting it into Bower. I have no idea how I would go about that, but one of the Bower creators coming over to play smash bros...will ask him.

<3

I really appreciate this :) Seems like Skeleton's greatest benefit is sometime to newcomers to RWD and knowing it helped someone learn a little means the most to me.

Also rad that you extended it. That's what it's about - making it your own :)

I wrote it totally by accident then got a dumb smile and was like...feels right.

Presumed the name came via "bare bones CSS framework"?

Thanks! Browser support is under a "catch all" more tab on site, but really should be in docs. I'll make it happen soon, though hopefully the readme is clear for now.

Thanks for opening the issue. Gonna dive into those very soon. appreciate you taking the time to add it to the list :)

Thank you for considering this. Skeleton is a great framework and I know a lot of people use it as a boilerplate. Regardless of your ultimate decision, I really do appreciate you looking into it.

I honestly hadn't considered this case. Let me dig into it and see if I can find a solution that works best all around.

>Sometimes you see all kinds of complicated workarounds for that, such as detecting an orientation change and temporarily blocking zooming, or detecting an attempt to zoom and then disabling the restriction temporarily so if the user repeatedly tries to pinch-zoom then subsequent ones work.

Chris_Newton's comment seems to have possible workarounds that can fix this issue. I'll trust your decision whatever you go with though, and thanks for Skeleton!

An option to increase text size in the interface is probably going to be even better than allowing zoom, since it will reflow the text and not require the user to scan left and right around the zoomed-in text.

Of course, this is how our browsers used to work before the makers decided to remove or hide that feature. I've never seen it on a mobile device. Does anyone understand the reasons behind that move? Even if you think page zoom is 'better' than text scale, surely it doesn't make sense to disable the latter altogether?

Awesome, thanks!