>>Tried this briefly (I assume you are referring to the first link?) But when using Safari with, say, an input element then the keyboard didn't kick in (but comes up when I change a url)
>>Are you seeing the same behaviour?
>
>It is acting strange. First of all, http://www.google.com does not respond. If you try http://www.microsoft.com, you will see that they keyboard comes out on the URL and the search but not on the site search.
>
>And, my assumption is that can only work with a touch screen, which is what those devices are intended for.

I don't think it is that. I could be wrong but I think that all of those emulators are still using the hosting browser engine to render a web page. If, for instance you are looking at the Ipad emulator using a Chrome browser then what you are seeing is how Chrome would render the page using the relevant viewport - not how Safari would neccessarily render it.

Same thing applies to any Javascript - the behaviour will be Chrome behaviour - not Safari ?

Bottom line : useful for a rough guide but not to be depended on....

I spent an hour yesterday getting the Nexus 7 debugger to work on windows - that allows me to see and debug the page *exactly* as it is rendered on the Nexus....