A good trick to get around this is to type location.reload() into
web-inspector.
On Fri, Feb 8, 2013 at 6:41 PM, Patrick Mueller wrote:
> Actually, interesting note on iOS 6 debugging - it's impossible to test
> 'normal' initialization, because you don't get the opportunity to debug a
> web app
Actually, interesting note on iOS 6 debugging - it's impossible to test
'normal' initialization, because you don't get the opportunity to debug a
web app until it comes up, and it's already been initialized.
If we want to support debugging initialization code, we could consider
delaying the initia
>JSHint reports ...
I created these way back when. The idea is to create debuggable cat'd
files, using the typical eval() with //@sourceURL hack, so you can see the
individual files in the debugger.
This didn't make much sense until iOS 6, on actual devices (but worked with
desktops, most of the
For initialization debugging methinks
On 2/8/13 3:13 PM, "Jesse" wrote:
>Can someone explain the use/purpose of the generated
>pkg/debug/cordova.***-debug.js ?
>JSHint reports they are just large collections of bad-escapements ... are
>these still used for something?
>
>--
>@purplecabbage
>risi
