The iPhone Safari debug console displays wrong error line numbers most of the time, especially on larger scripts. Desktop Safari is only slightly better.
1) For simple syntax errors you can use FireFox debug console which always identifies proper line number. 2) With Safari you may insert a simple test error line at different places in your script (e.g. in a binary search fashion) to help you locate the unknown error line. 3) You will also find that for errors in the same general source code area, the debug console tends to come up with line numbers which are wrong by the fixed offset from the actual error lines, such as actual_ln-shown_ln=172. Hence, after you find the first error instance you can use that line number difference to calculate the proper error line later, at least for a while. 4) Rebooting the iPhone will help in some cases. Other problems with the iPhone debug console are that it interferes with the screen metrics (it should be in its own window) and that it forgets the error list as soon as the page location changes (making it difficult to debug code that has to switch location). As result, I turn it off most of the time and use custom coded server support to dump debug messages from iPhone. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
