Bug 11208 - Macs fail to login quickly, Windows able to log in Instantly
Summary: Macs fail to login quickly, Windows able to log in Instantly
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 419.x
Hardware: Mac OS X 10.4
: P2 Major
Assignee: Nobody
URL: http://chaseonline.chase.com
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-07 10:59 PDT by Neema Aghamohammadi
Modified: 2022-07-06 15:31 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Neema Aghamohammadi 2006-10-07 10:59:51 PDT
Using Safari or Firefox, I am able to log in to my credit account eventually but it can take a very long time. Using Firefox or IE in Windows XP, I log in instantly. This seems to be a problem that plagues more than just Safari but how else can I report it?
Comment 1 Mark Rowe (bdash) 2007-01-07 02:44:20 PST
I would recommend also reporting issues with major sites like these directly to Apple at http://bugreporter.apple.com/.
Comment 2 David Kilzer (:ddkilzer) 2007-01-07 04:08:21 PST
(In reply to comment #1)
> I would recommend also reporting issues with major sites like these directly to
> Apple at http://bugreporter.apple.com/.

If you do not have an Apple Developer Connection (ADC) account to log into bugreporter.apple.com, you may create a free "online" account at https://connect.apple.com/.

Please note the bug number here that is assigned via bugreporter.

If you test this again (an if you report it through bugreporter), please note the versions of Safari, Firefox and Mac OS X that you're using.

CCing Mark Malone in case this turns out to be an evangelism issue (since it works, but works slowly on OS X).

Comment 3 Mark Malone 2007-01-08 08:55:29 PST
I have a chase account and it's pretty darn zippy - at least up to my expectations.   Give me a use-case, how long it took to complete and your connection type - I'll benchmark the same to see what I get.
Comment 4 Brent Fulgham 2022-07-06 15:31:50 PDT
There doesn't seem to be anything we can take action on for this bug.