JavaScript that works correctly in Firebird 0.6 fails in Mozilla 1.4

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
15 years ago
14 years ago

People

(Reporter: jdrash, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

My bank: (www.huntington.com) has an online banking interface.  In Firebird 0.6
when I click the a link (that runs a Javascript function) in my account register
to see the detail behind a transaction everything works perfectly. In all
versions of Mozilla 1.4 including the official version this does not work.  This
failure was introduced in 1.4, in previous versions this worked correctly.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

15 years ago
---> Browser-General; this is unlikely to be a JS Engine bug.
jdrash@eesus.jnj.com: are you seeing any errors in Mozilla's 

     Tools > Web Development > JavaScript Console?

(be sure to clear it of any previous errors first)
Assignee: rogerl → general
Component: JavaScript Engine → Browser-General
QA Contact: pschwartau → general
(Reporter)

Comment 2

15 years ago
In the Javascript Console there are errors.  I have verified something else.  
The problem with Mozilla 1.4 is happening on Windows XP and not Windows 2000.
> In the Javascript Console there are errors. 

Please paste those in this bug.

> The problem with Mozilla 1.4 is happening on Windows XP and not Windows 2000.

Does it happen on WinXP with a clean profile?

Comment 4

15 years ago
Boris: Bug 67603 (allow selecting multiple messages in JS Console)
seems to block some of what you've asked the reporter to do.
Um.. No, it just means it will take a few copy/paste operations instead of only one.
(Reporter)

Comment 6

15 years ago
JavaScript Console Output:

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIDOMWindowInternal.unescape]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
https://onlinebanking.huntington.com/default.asp :: FormatCurrency :: line 220"
 data: no]

Error: aTran has no properties
Source File: https://onlinebanking.huntington.com/default.asp
Line: 877

Error: aTran has no properties
Source File: https://onlinebanking.huntington.com/default.asp
Line: 880

Error: aTran has no properties
Source File: https://onlinebanking.huntington.com/default.asp
Line: 880

Error: aTran has no properties
Source File: https://onlinebanking.huntington.com/default.asp
Line: 886

Error: aTran has no properties
Source File: https://onlinebanking.huntington.com/default.asp
Line: 889

Error: aTran has no properties
Source File: https://onlinebanking.huntington.com/default.asp
Line: 896

Error: aTran has no properties
Source File: https://onlinebanking.huntington.com/default.asp
Line: 910

Error: aTran has no properties
Source File: https://onlinebanking.huntington.com/default.asp
Line: 924
(Reporter)

Comment 7

15 years ago
Someone asked if the error occurs with a fresh profile.  No a fresh profile give
the correct results.  My problem now, it what must I change in my exisiting
profile to make the problem go away.
What character coding is the page in when you see the failure?  What character
coding is it in when it's ok?  (According to the "View" menu.)

What is your default character coding set to in the two profiles?
(Reporter)

Comment 9

15 years ago
The Character Coding is the same in both profiles: Western (ISO-8859-1)
jshin, any ideas why unescape() would fail here?
(Reporter)

Comment 11

15 years ago
Why would a new "blank" profile work correctly and an existing profile fail? 
What  in a user's profile has to do with how JavaScript works?  I don't get this
at all. 
(Reporter)

Comment 12

15 years ago
Can anyone tell me what I need to do to make this javascript code work for an
existing profile?  Please, this is a huge problem.
Please attach your prefs.js from the non-working profile to this bug.
(Reporter)

Comment 14

15 years ago
Created attachment 128441 [details]
My prefs.js
(Reporter)

Updated

15 years ago
Attachment #128441 - Attachment description: My pref.js → My prefs.js

Updated

15 years ago
Attachment #128441 - Attachment mime type: application/x-javascript → text/plain

Comment 15

15 years ago
Can you upload  the diff. between attachment 128441 [details] and your working profile? If you 
don't have 'diff'',  just attaching your working profile would do.  
 
(Reporter)

Comment 16

15 years ago
Created attachment 128702 [details]
Prefs.js from the profile that works correctly
(Reporter)

Comment 17

15 years ago
Ihave have attached both prefs.js.  Again, I am confused as to what would cause 
unescape() to fail in 1.4 in a profile that worked correctly in previous 
versions. and why does it work correctly in 1.4 in a new profile.

What do I do next?
Hmmm.. if you create a new profile and put this prefs.js in it, does it
reproduce the problem?

If so, could you possibly narrow down which pref is responsible?
(Reporter)

Comment 19

15 years ago
Using the prefs.js from the "failing" profile in a new profile does not cause
the failure.  I guess the prefs.js file and its contents is not the problem.

What now?
hmm... move files one by one from the broken profile until you find one that
makes a difference?  I'd try bookmarks after prefs, I guess..
(Reporter)

Comment 21

15 years ago
FIXED in Mozilla 1.5b (build: 2003091004)

Ok, marking worksforme.  Please reopen if this reappears.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.