Closed Bug 503974 Opened 15 years ago Closed 15 years ago

First Direct online banking never finishes loading in SeaMonkey 1.1.x (Gecko 1.8.1.x)

Categories

(Tech Evangelism Graveyard :: English Other, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: raj, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.22) Gecko/20090605 MultiZilla/1.8.3.5i SeaMonkey/1.1.17
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.22) Gecko/20090605 MultiZilla/1.8.3.5i SeaMonkey/1.1.17

When logging into First Direct online banking, you can enter your authentication details but never finishes loading, making the site unusable.

I have tried with all extensions disabled (but not with a new profile) and get the same result.

Reproducible: Always

Steps to Reproduce:
1. From the URL, select "online banking"
2. In the new window/tab enter the username
3. In the second stage, enter the requested details and press "proceed"
Actual Results:  
The main screen on the online banking window partially loads but never finishes

Expected Results:  
The online banking site should fully load.

This site works as expected in Firefox 3.5, and a recently self-compiled build of SeaMonkey 2.0b1pre.  Needless to say, the site also works properly in IE7 and IE8.

If you spoof the user-agent of SeaMonkey 1.1.17 to include "Firefox/2.0" it also loads correctly.

This suggests that it could be a bug in Gecko 1.8.1 that is being worked around by browser sniffing for Firefox 2 on the server side, although I'm not sure.
How about Firefox 2? Does that work normally?

What's the user-agent string on the SeaMonkey build you compiled?
Works fine with Firefox 2.0.0.20 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20 (.NET CLR 3.5.30729)).

I'll try to get the SM2 UA later this evening.
(In reply to comment #1)
> What's the user-agent string on the SeaMonkey build you compiled?

The UA string is: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090614 SeaMonkey/2.0b1pre
And how about with the latest Minefield nightly (which, IIRC, doesn't have "Firefox" in it anywhere either)?
(In reply to comment #0)

> This suggests that it could be a bug in Gecko 1.8.1 that is being worked around
> by browser sniffing for Firefox 2 on the server side, although I'm not sure.

For the record, comment 2 pretty much disproves that, in case anyone else happens across this and thinks that's a possibility. The Gecko engine in Firefox 2.0.0.20 is (essentially, to within a security update or two) the same as the Gecko engine in SeaMonkey 1.1.7.

Raj, if you have access to a Mac, it would be helpful if you could test this in Camino as well. Let me know if you can test in Camino and I'll explain what you'd need to do.
Blocks: geckoisgecko
(In reply to comment #4)
> And how about with the latest Minefield nightly (which, IIRC, doesn't have
> "Firefox" in it anywhere either)?

Assuming that 'Minefield' is the codename for Firefox trunk nightlies (sorry, I use SeaMonkey pretty much exclusively), I grabbed the current build and it worked fine.

(In reply to comment #5)
> (In reply to comment #0)
> 
> > This suggests that it could be a bug in Gecko 1.8.1 that is being worked around
> > by browser sniffing for Firefox 2 on the server side, although I'm not sure.
> 
> For the record, comment 2 pretty much disproves that, in case anyone else
> happens across this and thinks that's a possibility. The Gecko engine in
> Firefox 2.0.0.20 is (essentially, to within a security update or two) the same
> as the Gecko engine in SeaMonkey 1.1.7.

I said in comment 0 that spoofing the UA (I set browser.useragent.extra.seamonkey2 to "Firefox/2.0") in SM 1.1.17 makes it work, which is why I suggested that they may be doing browser detection.

> Raj, if you have access to a Mac, it would be helpful if you could test this in
> Camino as well. Let me know if you can test in Camino and I'll explain what
> you'd need to do.

I'm afraid that I don't have access to a Mac, sorry.
If it was a bug in Gecko 1.8.1, they would need to treat Firefox 2.x and Seamonkey 1.1.x equally. They do not. Therefore, it's not a workaround for a Gecko bug.
Right now its 404ing, im not going to close this bug yet.
There is a link on http://www.firstdirect.com/ that takes you to the Online Banking page (I ended up at www2.banking.first-direct.com).

This now WFM with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0
Based on comment 9, this sounds FIXED.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.