I also see a horizontal scrollbar, scrolling right reveals the second vertical scrollbar.
It's a nice idea, but the usability for PC users is terrible. Hopefully you can fix that in future iterations.
We have that html as a development-only page in our framework, so when developing/designing a site we can go to /responsive and test it that way, very convenient.
Also, the output for http://mattkersley.com/ doesn't match in any way his responsiveness test at http://mattkersley.com/responsive/
A bookmarklet would be great too
Actually, it's once you're looking at a page in a subdirectory of your own server's doc root, for any URL, not just localhost:PORT#.
Click it to quickly wrap any site in responsive.is.
Pros: saved an insane amount of time - a dozen templates instantly became 48 templates because each page had 4 resolutions.
* it was awkward to resize the browser window 4 times per page, so this Responsive.is tool would've helped immensely, especially with how it highlights the active window port and allows the rest of the content to be masked but still faintly visible, so the layout doesn't feel cramped because you can see a quick preview of the rest of the content "below the fold".
* the default Bootstrap styling is so plain that it felt like half of the critiques were about the boxiness of the visual design, not the visual hierarchy of the information itself. Themes wouldn't help for this particular client because they're a big giant company that have their own branding anyway.
So prototyping with Bootstrap gave me way more templates in a short of amount of time but it's ugly enough that stakeholder critiques were distracted by it (which is why I usually stick to high fidelity mockups and use wireframes only for internal team collaboration, if at all). More production-ready in some ways (the frontend dev on the team finally got engaged with feedback and is ready for handoff) and less in others (stakeholders won't give real feedback until they see it styled with polish).
This isn't IE6, it's FF7, which is 5 months old!
Edit: For some reason, http://responsive.is/trentwalton.com now works fine. A Quirk, perhaps?
Used Skeleton's 12-column CSS framework, which was a bit buggy. Has 4 breakpoints - 960 width, ipad portrait, iphone landscape and iphone portrait. The gray border up top represents where the menu will reside and scale. I'm not thrilled with how we handled the transition to mobile - the varying blocks of text in 'who we are' and the subsequent example need to be more differentiated.
Actually modern mobile browsers can handle unresponsive layouts quite well, often better than some "responsive" Layouts.
<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1, maximum-scale=1">
What about random or next/previous buttons in the header in addition to the dropdown?