Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008032801 Minefield/3.0pre Hm, I see no error at all. Maybe caused by add-ons? Do you see the same in safe-mode? http://kb.mozillazine.org/Safe_Mode_(Firefox)
Hm, Google knows exactly where I should be. Still no error at all, though.
Safe mode doesn't fix it for me. I also had this exact same problem on my work computer with firefox 3 on it (no add-ons on that one). The errors I get are "unterminiated string literal" or "missing ) after argument list" I have to go to the error console to see them, as the only indication on the page that it failed is that the status box on the bottom right of the page gets stuck in "updating" and none of the targets that should be overlayed on the map get drawn.
I tried also the build you're using, in case it was fixed in the meantime, but still nothing, only yellow warnings, no errors.
Do you see any targets overlayed on the map? maybe you're in an area with none to draw and therefore it works without error. Try going moving the map to a densely populated area in the US or Europe (the east coast of the US for example). I gets MANY errors when I move the map around as it keeps trying the redraw targets during zoom/location changes and errors during each attempt.
It seems to work normally. When I click on a blue marker I get a balloon with weather information etc. Works the same here as in Firefox 2.
Very odd.. I don't know why my setup is broken. I first saw this on my work computer and last night at home I did a first time install of firefox 3 beta 4 to ensure it wasn't just that one machine before entering the bug. Anything else I can try to narrow this down?
I'd first try a new profile, maybe it is just some setting. http://kb.mozillazine.org/Profile_Folder
Well, it behaves a little different with a new profile, but it still doesn't work. Now the errors I'm seeing include "Obje is not defined", "Obj is not defined", "no element found", and "xmlreq.responseXML is null"
Really mysterious. Maybe you could try a clean install? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ Just download the zip-file, unzip it on your desktop and start the firefox.exe inside it.
Created attachment 312498 [details] sampling of random errors adding error console screenshot. You can see some of the errors end in "%2" where the next expected character was a 'space', hence my previous comments about truncation of html coded characters...
In addition to seeing this problem on FF3, I have also seen it on Epiphany on Ubuntu 8.04 beta. I believe that this indicates that it is potentially a Gecko problem (Epiphany is Gecko based) and not specific to Firefox...
If it doesn't reproduce right away, it can be usually be triggered by zooming out a bit to show some more tracking targets (... bigger XML blob ...).
I always get this with an Intranet site (Replicon Timesheet 7.2 from www.replicon.com), using FF3.0b5 (under WinXP). FF2 is fine. I suspect this is also bug 355567.
This still reproduces with 3.0 RC1. FF2.0 works fine. I don't think this matches 355567. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0
Errors appear on Mozilla/5.0 (Windows; U; Windows NT 6.0; pl; rv:1.9) Gecko/2008052906 Firefox/3.0 Most of the time there are no objects shown on the map and the site shows "updating" status. Steps to reproduce: 1) Enter aprs.fi and log in using any text. 2) Enter "Wroclaw, Poland" in address field. 3) Look at error console
tested on Shiretoko (firefox 3.1 Alpha 1) and the problem still exists.
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 3.0 Branch
I am no longer seeing this issue in FF 3.6.x or 4.0 prerelease versions...
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.