Closed Bug 467700 Opened 17 years ago Closed 15 years ago

Firefox does not execute script

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: notinthehead, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2010-11-01])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 [code] <ul><a href=javascript:Dispatch('PROGRAM','Programhandbooks/gotoProgram.asp|BSIT/BSA|006')><li>BSIT/BSA - 006</li></a><div id="BSIT/BSA_CTS"></div><script>getContacts('8905290236','BSIT/BSA','006');</script><BR></ul> [/code] Firefox does not execute this section of the code: [code] <script>getContacts('8905290236','BSIT/BSA','006');</script> [/code] The code functions in IE. I can send screen shots if necessary. Reproducible: Always Steps to Reproduce: 1. Log into my account at University of Phoenix 2. 3. Actual Results: All code around that <script> tag executes. But nothing in the scrip tags. The software should run the code and run the script.
Maybe you see an error in the error console (under Tools)?
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.