Closed Bug 425586 Opened 16 years ago Closed 14 years ago

javascript doesn't run that works fine on firefox 2.0


(Firefox :: General, defect)

3.0 Branch
Windows XP
Not set





(Reporter: zach, Unassigned)




(Whiteboard: [CLOSEME 2010-07-30])


(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4

I see javascript errors on that did not occur with firefox 2.0.  I have reported this to the website owner, but I'm not sure if it's a problem with the site or with firefox 3 (since it works fine with firefox 2.0)...

Reproducible: Always

Steps to Reproduce:
1.go to
2.look at error console
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?
Sorry, I forgot about cookies.  When you go to, you have to 'login'.  Just give it a nickname and click 'login'.  It's the google map page with javascript that gives the errors.  It should draw a bunch of stuff over the map, and depending on zoom level it'll sometimes draw a few things or nothing before erroring out.
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.
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?
Just download the zip-file, unzip it on your desktop and start the firefox.exe inside it.
Still have errors with using the zipped nightly...  It look like the errors are all related to the javascript info being cut short.  "syntax error"s and "missing )" and the such.  The little green arrow in the error console is always right at the end of the line that obviously looks like it's been cut short.  Could this be ISP related (both my work and I use time warner cable for ISP).  maybe firefox 2 and 3 do requests for xml data differently or something and the firefox 3 requests result in very long return data that gets truncated somewhere?
I also booted my machine using Ubuntu 8.04 beta, which includes firefox 3 beta 4 on the CD.  That setup exibited the same javascript errors that I have described here...

It seems that the errors frequently are reported for an obviously incomplete line that ends in "%", which is another reason I feel like the (XML?) data stream is being cut off somehow (like a HTML coded character didn't make it all the way through and was cut short right after the "%").
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...
Ok, trying with both Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4 and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20080311 Firefox/

As far as I can tell I'm able to replicate the fact that there are errors but the exact error isn't reproducible.  Like Zack is saying, it seems that the errors related to randomly truncated javascript on eval lines.

Here are my steps to reproduce:

Go to and login with a random login.
Then navigate to Atlanta, Georgia.  (You can enter it in the box in the right hand pane, press enter)
Then click on Show All next to Track callsign in the right hand pane.

Check the Error Console.

In FF2, no errors.  Lots of things show up.

In FF3, some errors.  (The exact error seems to be inconsistent).  Nothing shows up.
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...
I'm the author of I could reproduce this on Firefox 3.0b5 - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5

It would seem like something in the AJAX interaction. The site works fine with FF2.0 and 1.0, MSIE 6.0 and 7.0, Konqueror, Opera and Safari. There might be something stupid in my AJAX implementation, but this still seems like a Firefox or Gecko bug to me at the moment.

The javascript on the site does XMLHttpRequests to the site, gets back XML which contains child elements containing escaped javascript code. There is sometimes quite lot of XML and javascript in the response. The child nodes are unescaped and then executed using eval() like this:

for (var jse = 0; jse < xmlfeed.childNodes.length; jse++) {
  if (xmlfeed.childNodes[jse].tagName == "js") {
    var evaljs = unescape(xmlfeed.childNodes[jse];
    //dump("evaluating: " + evaljs + "\n");

I enabled some logging on the server to see what goes in the XML. This javascript is generated on the server (intended to be evaluated by the above piece of code):

TCPIP*,qAC,CORE-2','igate testing')

It goes into this piece of XML, special characters encoded:


This is what the Javascript error reported on the Error Console said for the above line (when eval()'ing it):

missing ) after argument list

It seems to fail at random spots in the evaluated javascript - it would seem like the javascript is truncated somehow, somewhere. Next, I added dump()'s to the javascript - one before the eval (like above) and one dump of xmlreq.responseText just after the response has been obtained.

It would seem to me that xmlreq.responseText does contain the whole XML blob as generated by the server. But for some reason, the parsed XML child elements are truncated. They're truncated before the unescape() call. If I dump xmlfeed.childNodes[jse] - it is sometimes truncated even though a previous dump of xmlreq.responseText was not truncated.
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, 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 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.
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...
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.