Closed
Bug 59287
Opened 25 years ago
Closed 24 years ago
Unable to log in to excite mail or my excite page
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jt.marsh, Assigned: asa)
References
()
Details
(Keywords: qawanted)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.17 alpha; en-US; m18) Gecko/20001106
BuildID: 0000000000
When attempting to log in to either my excite page or my excite email,
authentication fails for some reason and I end up on a page which asks me to
re-enter my username and or password.
Reproducible: Always
Steps to Reproduce:
Go to www.excite.com.
Click the sign in URL.
Enter user name and password.
Click submit.
Actual Results: I get lots of java script errors before getting to a page which
asks me to re-enter my user name/passowrd.
JavaScript strict warning:
http://reg.excite.com/mps/loginreq?pname=mail&brand=xcit&targeturl=http%3A%2F%2Finbox.excite.com%2F&select=1
line 417: reference to undefined property padding[i]
Error was suppressed by event handler
JavaScript strict warning:
http://reg.excite.com/mps/loginreq?pname=mail&brand=xcit&targeturl=http%3A%2F%2Finbox.excite.com%2F&select=1
line 417: reference to undefined property padding[i]
Error was suppressed by event handler
Expected Results: I expect to see my excite web page.
I don't suppose you'd be willing to give us a username and password to
reproduce? And considering the javascript errors their page could be wrong.
I suspect we use DEC to represent Alpha.
Since neither of my excite accounts work, I assume this problem is not specific
to my user id and you can create an account for you to use for testing.
While it well may be a problem with excite's page, that doesn't explain why it
works when I use m18 compiled for ppc linux, and doesn't work when using alpha
linux (same sources, just different platform).
Comment 3•24 years ago
|
||
Reporter are you still seeing this on the latest nightlies?
Comment 4•24 years ago
|
||
I am marking this WORKSFORME due to the lack of update from the reporter and
because nobody is able to reproduce this.
Reporter, please feel free to reopen this bug anytime if you can reproduce with
a nightly build (http://ftp.mozilla.org/pub/mozilla/nightly), or with the
upcoming mozilla 0.7
Thank you a lot!
Fabian.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•