Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Had Firefox for long time. Recently I've had big problems using Yahoo IM through email that doesn't happen with Internet Explorer. What gives? I'm not a techie btw.

  • 3 replies
  • 2 have this problem
  • 4 views
  • Paskiausią atsakymą parašė the-edmeister

more options

In the past week I have begun to experience all kinds of problems with my yahoo account so I'm not sure if it's Firefox or Yahoo that has issues but it does not happen when I use Internet Explorer. I have always IM through Yahoo email. Now when I click on the individual that is online the chat window does not materialize.

In the past week I have begun to experience all kinds of problems with my yahoo account so I'm not sure if it's Firefox or Yahoo that has issues but it does not happen when I use Internet Explorer. I have always IM through Yahoo email. Now when I click on the individual that is online the chat window does not materialize.

All Replies (3)

more options

Known issue, our QA team working on it, See

you can follow the bug by opening bugzilla account and add yourself to CC list :)

more options

Swarnava, your answer was too generic for me. I am techie challlenged. You said for me to "you can follow the bug by opening bugzilla account and add yourself to CC list :)" I followed the link to bugzilla account and created one. So I'm supposed to add myself to CC list of what?

I need detailed step by step instructions such as do A first, then do B, then do C, etc.

more options

Comment 7 in that Bug report has a fix that a novice use should be able to handle.

 I found a workaround to get chat to work.

STR:
1. Go into your Yahoo Messenger Options - Change the Window in the dropdown to Tab and press OK.
2. Then go back and switch it to small window and press OK.

After that I can get the chat window to launch. I tested on Mac as well as that workaround works. 

Looks like Firefox 10.0 isn't affected.

Modified by the-edmeister