3 ms·
This looks like a pretty good last resort. I find that majority of iPad issues can be solved by just resizing safari to the iPad dimensions. Most issues I come
by VonLipwig 15y ago
This looks like a pretty good last resort.
I find that majority of iPad issues can be solved by just resizing safari to the iPad dimensions. Most issues I come across appear on both platforms so troubleshooting isn't too bad.
- sirn 15y agoIt works well, except when you have to deal with a really mobile specific stuff (e.g. -webkit-min-device-pixel-ratio, -webkit-text-size-adjust) then you're left with no choice but to debug it on actual device (or in a simulator) although using Firebug on a small screen device is really awkward. WebKit Remote Debugging[1] would be an ideal solution when it lands. For the time being, weinre[1] looks like a good (stopgap?) solution. [1]: http://www.webkit.org/blog/1620/webkit-remote-debugging/ http://www.webkit.org/blog/1620/webkit-remote-debugging/ [2]: http://phonegap.github.com/weinre/ http://phonegap.github.com/weinre/
- vital101 15y agoWe use Weinre for remote debugging of iPads and it has worked out very well for us.