Closed Bug 256651 Opened 21 years ago Closed 20 years ago

can not open the yahoo mail from www.yahoo.com (Returns Do you Yahoo?)

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED EXPIRED

People

(Reporter: jmuel86, Assigned: bugs)

References

()

Details

(Keywords: top100)

Attachments

(2 files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 The yahoo email http://www.yahoo.com link mail does not open up the yahoo email. Instead it opens up Do you Yahoo? Reproducible: Always Steps to Reproduce: 1. Go to http://www.yahoo.com 2. click on the mail link 3. Actual Results: Do you Yahoo? displays Expected Results: Opened up a web page to enter in username and password.
Version: unspecified → 1.0 Branch
Component: Web Site → General
(In reply to comment #0) > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 > Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 > > The yahoo email http://www.yahoo.com link mail does not open up the yahoo email. > Instead it opens up Do you Yahoo? > > Reproducible: Always > Steps to Reproduce: > 1. Go to http://www.yahoo.com > 2. click on the mail link > 3. > > Actual Results: > Do you Yahoo? displays > > Expected Results: > Opened up a web page to enter in username and password. Test Environment XP Pro, Service Pack 2 and all other patches. Clean install of Firefox 1.0 Preview Release. Steps: Went to http://yahoo.com and http://mail.yahoo.com/?.intl=us. Clicking on the Email icon directs me straight to the Yahoo email logon page. Could not recreate the issue. Perhaps deleting the cache and cookies will resolve this.
This WORKSFORME, Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10, under Windows XP.
I confirm, with win2k, XP, linux mdk 9.2 updated, firefox 1.0 updated 1.0.1, with or with out extensions. in fact FF receives the cookies but loops back on the login page. galeon works fine (no loop back). after first identification and cookie received, go back to yahoo main page et click mail, you go right through your mailbox.
I also find that I can not read my yahoo mail with Firefox. It seems that when you go to the yahoo pages not all of it comes through clearly or not at all.
wfm
I have just upgraded to 1.01 and cannot access my yahoo mail account, it just gives me a blank page. I am having to run ie to get at my mail. Not what i want.
If this is an intermittent problem then it's probably their fault. If its 100% repro on a per-user basis then it's probably ours.
Keywords: top100
(In reply to comment #6) > I have just upgraded to 1.01 and cannot access my yahoo mail account, it just > gives me a blank page. I am having to run ie to get at my mail. Not what i want. This also is my experience. It's interesting the Firefox (1.0) previously worked for acquiring e-mail through My Yahoo, but all of a sudden it stopped. IE works well, but I want to use Firefox! BTW, I am using Win XP, and the e-mail problem is recurrent and reproducible. Any help would be appreciated. Thanks...
I have experienced the same problem with a blank page after logging into mail.yahoo.com. I am attaching the HTML that was sent back by the yahoo server. Also, the following error shows up in the JavaScript Console Error: removeCookie is not defined Source File: http://us.f209.mail.yahoo.com/ym/login?.rand=55a07q1monf73 Line: 121 This removeCookie function is defined in another JS file loaded by this page. I will attach that file as well.
According to me, the problem is due to FF : I've saved the page locally, with the mailcommonlib.js, and then called it in FF. This give me access (strangely?) to my Yahoo!mailbox !! Here is what happened (list of calls from the LiveHTTPHeaders extension) : http://127.0.0.1/tests/test_debug.html : ======================================== GET /tests/test_bug.html HTTP/1.1 Host: 127.0.0.1 HTTP/1.x 200 OK ---------------------------------------- http://127.0.0.1/tests/mailcommonlib.js GET /tests/mailcommonlib.js HTTP/1.1 HTTP/1.x 304 Not Modified ---------------------------------------------------------- http://127.0.0.1/ym/instacompose?sobakafrnull GET /ym/instacompose?myaccountnamenull HTTP/1.1 Referer: http://127.0.0.1/tests/test_bug.html HTTP/1.x 404 Not Found ---------------------------------------------------------- http://fr.f263.mail.yahoo.com/ym/welcome?YY=75344&rand=1115583397249 GET /ym/welcome?YY=75344&rand=1115583397249 HTTP/1.1 Host: fr.f263.mail.yahoo.com HTTP/1.x 200 OK ======================= (END OF REPORT) ===================== So locally, all is OK : the javascript file is called just after the main document : it's normal because it's a link.. (and I can have acces to my mails ;) However, the situation is different online : when you look at the list of calls when you submit the login formular, the javascript file mailcommonlib.js isn't called at all : =============================================================== GET /config/login?.done=http%3A//mail.yahoo.com&.tries=1&.src=ym& ... HTTP/1.1 Host: login.yahoo.com HTTP/1.x 302 Found ----- GET /config/verify?.done=http%3a//fr.f263.mail.yahoo.com/ym/login%... HTTP/1.1 HTTP/1.x 302 Found ----- GET /ym/login?.rand=dvvfnhtjgunt0 HTTP/1.1 HTTP/1.x 200 OK ========================= (END OF RECORD) ============================= and that's all ! After 2 redirections, the main document (corresponding to my test_bug.html), but no javascript file !!! Can anybody find an explaination to this comportment ? Should I post this addendum to another bug report ??
Confirmation with “Venkman”, the JavaScript debugger : - online, no javascript file, 'login' only (so-called by the debugger) - offline/locally : 'test-debug.html' + 'mailcommonlib.js' (nota : I first saw this, but I thought that this strange result was due to the debugger)
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: