Welcome to the MacNN Forums.

awaspaas · Jan 16, 2003, 01:36 AM

Well, turns out it was too good to last - even though Wells Fargo online worked fine with Safari, they decided to deny it starting today. Guess IE's back in the dock.

Severed Hand of Skywalker · Jan 16, 2003, 01:47 AM

Originally posted by awaspaas:
Well, turns out it was too good to last - even though Wells Fargo online worked fine with Safari, they decided to deny it starting today. Guess IE's back in the dock.

Wells Fargo?

Gul Banana · Jan 16, 2003, 01:51 AM

Send them a message! That's such an annoying thing to do.. if their site works fine in Safari, why on earth should they force people to use IE?

Edit: I just saw the following "For your protection, Wells Fargo does not support beta versions of browsers. Under normal circumstances, Wells Fargo will support the final version of a browser approximately two weeks after the release date." I suppose that's reasonable.

awaspaas · Jan 16, 2003, 01:55 AM

Heehee I showed them! Set my user agent to Netscape 7.0 and now it works. Heh, take that Wells Fargo!

awaspaas · Jan 16, 2003, 02:00 AM

Originally posted by Severed Hand of Skywalker:
Wells Fargo?

(very popular bank around these parts)

BTP · Jan 16, 2003, 03:14 AM

If you want, go get Safari Enhancer and you can set Safari to identify itself as most any browser/OS as you want.

awaspaas · Jan 16, 2003, 03:17 AM

Originally posted by BTP:
If you want, go get Safari Enhancer and you can set Safari to identify itself as most any browser/OS as you want.

Right. See three posts above.

Xeo · Jan 16, 2003, 03:18 AM

They don't have to support a beta browser. That doesn't mean the have to kill it, either! I mean, what the hell? How could their banking system have problems by simply not blocking it? If it causes problems for the user, it's up to the user to change their browser. Geez.

That simple disclaimer they have is enough to tell people with problems that they won't do anything.

awaspaas · Jan 16, 2003, 03:29 AM

Originally posted by Xeo:
They don't have to support a beta browser. That doesn't mean the have to kill it, either! I mean, what the hell? How could their banking system have problems by simply not blocking it? If it causes problems for the user, it's up to the user to change their browser. Geez.

That simple disclaimer they have is enough to tell people with problems that they won't do anything.

I'm gonna remain confident though - they've been very good with Mac support in the past and I have no reason to believe they won't support Safari once it's gone final.

But if they don't, then there's gonna be some ass-whoopin'!

wataru · Jan 16, 2003, 03:35 AM

Viva la Debug menu!

Jasoco · 11:52 AM

Edit: Nevermind. Found my answer.

Dale Sorel · Jan 16, 2003, 12:10 PM

OK, now I know I'm not going crazy

I thought it was working the other day

Those jerks, good thing there's the debug menu to save the day

Millennium · Jan 16, 2003, 12:16 PM

This is where the Debug Menu comes to the rescue.

Under mormal circumstances, I'd say that there's no need for Wells Fargo to take action. But they're a banking site, and Safari is a new, relatively untested browser, still in beta. If a security hole were to be found, that could mean a lot of financial information leaking out. So frankly, I'm not sure they had much of a choice in the matter. Annoying as it is, one might even say that it was the right thing to do.