> why? I don't know... it works for me on FF, IE8 and Chrome, all on windows. I don't have access to a Mac, so it's hard to see what's going on there.
>it's a problem on my script or it depends on browser's configuration > for execute javascript? quite possibly. I would guess that part of it has to do with the other javascript errors that your page shows. in Firebug, the first is: "ActiveXObject is not defined" (line 49 of gears_init.js) the second is "joms.jQuery.fn.qtip.timers is undefined" (Line 1737 of gears_init.js) the third is: "value.initialize is not a function" (Line 25 of gears_init.js) so I would say that you are having problems with the gears_init.js file, there at least anyway. How do your browser tests work on the original example you had: http://www.urbanclaim.com/new.php ? The thing is that firefox is very forgiving on js errors and tends to battle through regardless. Other browsers can just freak out and freeze up when they hit a piece of code they don't like. > can you help me? not really. If you're happy with how W3 performs you could delete the tryGoogleGears and tryGoogleLoader functions (and the code that calls them, at the end of the W3 attempt) and not load gears_init.js at all and see if that improves things. Otherwise it's very hard to tell without seeing the errors what's going wrong. You really need to learn to use the debugger in the browsers where you are experiencing problems, or at least insert alerts in your code so you can tell what is happening. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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/google-maps-api?hl=en.
