Glad you solved it.
In general, IE is more precise on syntax. For example FF doesn't care
about extra commas, whereas IE stops into the first syntax error. That
is, as far as I know.
- mika
Bill Thoen kirjoitti:
Nicholas Bergson-Shilcock wrote:
This post gives instructions for using the free (as in beer) Visual Web
Developer Express to make IE debugging a little less painful. I've found it to
be quite helpful in tracking down JavaScript issues with IE7:
http://www.berniecode.com/blog/2007/03/08/how-to-debug-javascript-with-visual-web-developer-express/
Hope this helps,
-Nick
Thanks, I managed to find the big problem using Firebug lite (I had
mis-deployed one of the files (openlayers.js) in my Windows environment.
It was a case of case--I didn't name a file correctly.) And I discovered
that the line numbers make sense if you can guess which js module to
open (the IE error reporter always says the error is in the main html
module, even if it's in a *.js file.)
Thanks for the help, guys!
- Bill Thoen
_______________________________________________
Users mailing list
[email protected]
http://openlayers.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://openlayers.org/mailman/listinfo/users
