119952 - On Linux Alpha - unable to login to my excite or excite email

Status: VERIFIED DUPLICATE of bug 121115

(Core :: DOM: Core & HTML, defect)

Description

[jt.marsh]

From www.excite.com or my.excite.com, I can't log in to my page or my excite
email using Mozilla running linux on alpha. On linux ppc, I can login without
problems.

After entering my user id and password, there is a delay after clicking the
submit button where it doesn't seem anything is happening, after which I always
end up on a page re-asking for my id and password.

Since this works fine on other platforms, it seems like a 64 bit javascript problem.

Comment 1

[Phil Schwartau]

Browser, not engine. Reassigning to Form Submission.

[e-mail]: do you see any errors in Tasks > Tools >
JavaScript Console? (be sure to clear it of previous errors)

Comment 2

[jt.marsh]

I don't see any errors in the javascript console.

Comment 3

[Andrew Schultz]

can you log in with JavaScript disabled?
see also bug #121115 (similar problems on Yahoo)

Comment 4

[Andrew Schultz]

Looking at the HTML source at Excite, this could be a dupe of (or at the very
least depends on) bug 121115.  The Excite page also uses MD5 encoding/hashing in
JavaScript, and the problems described in bug 121115 are probably screwing that
up here as well.

Comment 5

[Alexandru Savulov]

anyone has a test account?

Comment 6

[Vladimir Ermakov]

login:mozillatest
pswd: mozilla

Comment 7

[Andrew Schultz]

I can confirm that it doesn't work on Alpha-Linux (build 20020327), but based on
the behavior of bug 121115, I still think this has to be a dupe.

Comment 8

[Phil Schwartau]

I agree this is a duplicate. I have no trouble logging in to the 
test Excite email account with my Pentium Linux Red Hat 7.2 box.
And the the reporter of this bug had the same experience:

> I can't log in to my page or my Excite email using Mozilla running
> Linux on Alpha. On Linux PPC, I can login without problems.

The descriptions of the two bugs, and the confinement of the problem
to Alpha chips convince me that this is the same issue. 

Expert work by Andrew and Brendan in bug 121115 showed this to be
a complier bug, not a bug with Mozilla. Andrew has filed a bug
against Red Hat on this issue: 

  http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=61154


So, I'm marking this a duplicate. Please reopen if you disagree -

*** This bug has been marked as a duplicate of 121115 ***

Comment 9

[Andrew Schultz]

verified dupe