Closed Bug 81785 Opened 23 years ago Closed 23 years ago

Cannot login to My Yahoo

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: mseitz, Assigned: asa)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9) Gecko/20010505
BuildID:    200105015

I tried to login to My Yahoo (https://my.secure.yahoo.com) for the first time
since installing Mozilla.  Each time I entered my account name and password, I
was taken back to the initial login screen.  However, when I closed the window,
and then opened a new window and entered the same URL, I was automatically
logged in and the My Yahoo screen for my account displayed correctly.

Reproducible: Couldn't Reproduce
Steps to Reproduce:
1.  Go to https://my.secure.yahoo.com
2.  Enter account name and password.


Actual Results:  My Yahoo initial login screen appeared again 

Expected Results:  My Yahoo page for my account should have appeared.
Component: Preferences → Browser-General
This behavior was also reported in bug 81696 when logging in to excite.  
Probably a dup.
browser general
Assignee: mcafee → asa
QA Contact: sairuh → doronr
I agree, the behavior in later comments of bug report 81696 does look to be the 
same bug.  Sorry if this turns out to be a duplicate.
this works for me.  Looks like my.yahoo.com switched to
some JS login?  It used to be another page, there looks
like new content to me.  I'm on 5/19 bits, w2k.
After reading the previous comment, I downloaded the "nightly build".  With 
this new version, I do not see the problem:
Mozilla 0.9+
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9+) Gecko/20010519
Build ID:  2001051920

I can still reproduce the problem with:
Mozilla 0.9
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9) Gecko/20010505
Build ID:  2001050515
marking worksforme per reporter
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
I was wondering why this was marked as "WORKSFORME" instead of "FIXED", since I 
was able to reproduce the problem with the 0.9 milestone build.
Matt, Fixed is reserved for bug reports which were actually assigned to a
developer and fixed.  This report does not meet that criteria.
Understood.  What confused me was the definition of "WORKSFORME":

"All attempts at reproducing this bug were futile..."

Since I had reproduced the bug, I thought this did not apply.  Perhaps this 
should read 

"All attempts at reproducing this bug in the current build were futile..."


v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.