Created attachment 283335 [details] Screenshot of errors Yahoo yesterday (10/2) updated its yahoo mail beta but it appears only for its paying customers since my gf's account is still the same. Anywho there are two errors after logging in after the page loads and no emails ever open in the viewing pane and always get the message about the page taking too long to load and that I should switch to yahoo mail classic...that is currently the only way I can read my emails.
Can you find a regression range?
(See also bug 396683)
Works Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/2006112204 Minefield/3.0a1 Broken Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/2006112304 Minefield/3.0a1 Regression range: http://tinyurl.com/ynqxno My bet is bug 47903
Judging by bug 47903 dependencies, this is not a regression but supposed to happen because of some technical stuff and bugs filed because of it are marked tech evangelism so I'm changing this ones product and component. Hopefully the second error is also related?
(In reply to comment #4) > Hopefully the second error is also related? Oh, can you please test this with 2006112204 vs. 2006112304?
Yahoo already fixed a similar problem once (see bug 361709).
Dao yeah same regression range just there were a bunch of checkins that day...slight possibility of a coincidence but who knows. I can't find the archived hourlies to narrow down the regression range even further.
Yes, although I haven't diagnosed it, it seems like a new instance of bug 361709. Most likely new code in the new release. I'm sorry but we have not been actively testing against FF3. I filed a bug internally for us to track it.
Is it safe to assume this affects any trunk-based browsers (i.e., Camino and Seamonkey trunk builds), not just Minefield?
note: this affect not only paying user from Yahoo, this affects also users in germany of the free service, since we don`t have the exact same premium system here with yahoo mail.
yup, im a user of yahoo mail free and i am seeing this bug. hoping this will be fixed (by yahoo) before beta.
I think its now out of beta and final for yahoo mail so this will be more of a problem for firefox 3.0 beta 1 users now.
Yup - confirming that I'm seeing this with FF 3.0b1 RC1 candidate. I've been forced to go back to the classic ui. Can we please update the severity of this one? Lots of free users have also moved to the new UI, and all will be affected. If it's tech evangelism, someone needs to push Yahoo to fix their UI. Else a workaround is needed..
I have a free account and when I login to yahoo I get the beta UI. In Fx3b1rc1 it does not work. I think many more users will be seeing this if they are using the beta interface. As Shankar points out, you need to switch to the classic UI to check your mail, otherwise frustration will ensue. Can someone put some oil in the machinery so this gets resolved on either end as soon as possible?
I think it's save to assume that Yahoo will fix this after Beta 1 is released. The error is descriptive and all.
(In reply to comment #17) > I think it's save to assume that Yahoo will fix this after Beta 1 is released. Thus far, Yahoo has averaged a fix for about one-third of the total TE bugs filed against them (I'm giving them the benefit of the doubt and assuming that WORKSFORME bugs were actually fixed). This is not exactly a stellar track record, nor is it any grounds for "safe assumptions" by any stretch of the imagination. The only reason I have any hope that they might fix this is that it affects *all* Gecko consumers (including Firefox), and to ignore Firefox is effectively financial suicide for an Internet company. I certainly wouldn't get any hopes up about a fix prior to Firefox 3 being released, though.
Just received word an hour ago from the Yahoo Mail team. Darren James and his team have a fix ready. Current state is its being tested in their staging servers by QA. (a few layout issues still pending) Cc'ing darren to the thread.
During Litmus testing, I hit this bug when running ctalbert's litmus test case. This is the error that showed up for me in the console: Error: junk after document element Source File: http://us.mg2.mail.yahoo.com/dc/launch?consentLW=1 Line: 1, Column: 416 Source Code: <menu id="themes" title="Colors" beforeshow="beforeThemeMenu"><item cmd="theme" id="_blue" cmdData="blue">Ocean</item><item cmd="theme" id="_sand" cmdData="sand">Chrome</item><item cmd="theme" id="_gold" cmdData="gold">Tangerine</item><item cmd="theme" id="_plum" cmdData="plum">Violet</item><item cmd="theme" id="_lime" cmdData="lime">Grass</item><item cmd="theme" id="_pink" cmdData="pink">Bubblegum</item></menu><divider id="theme_divider"></divider> ctalbert suggested I add this info to the bug. Also, his test case at http://people.mozilla.com/~ctalbert/test-mailto-yahoo.html may have to be adjusted if Yahoo makes changes on their end, just mentioning this for tracking purposes for our Litmus test cases.
We do not have any outstanding NS_ERROR_DOM_WRONG_DOCUMENT_ERR errors that I'm aware of (in our latest development builds). There was one that happened during launch that I fixed a couple of weeks back, but the bug did not prevent the launch from proceeding. I'll have someone on the team follow up.
I have lots of NS_ERROR_DOM_WRONG_DOCUMENT_ERR accessing Yahoo! Mail. I thought at first it was because of the Yahoo! Mail Notifier Extension, but it happens when I visit the web page. The specific error code is: Error: uncaught exception: [Exception... "Access to property denied" code: "1010" nsresult: "0x805303f2 (NS_ERROR_DOM_PROP_ACCESS_DENIED)" location: "<unknown>"]
This is 100% reproducible for me on: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b1) Gecko/2007110903 Firefox/3.0b1 I get the same error as comment #20 in the error console. I also get a Loading Yahoo! Mail message in the upper right hand corner, with text saying "Mail appears to be taking longer to load than usual. This could be a temporary glitch. Try refreshing your page. Or for this session only, click here to see if Mail Classic loads faster."
(In reply to comment #23) > I also get a Loading Yahoo! Mail message in the upper right hand corner, with > text saying > > "Mail appears to be taking longer to load than usual. > > This could be a temporary glitch. Try refreshing your page. Or for this session > only, click here to see if Mail Classic loads faster." > Yeah, the Yahoo! Mail beta and Minefield do not play well together and I was getting that error with a5 builds. Oddly enough at about the same time that attachments stopped working between Mail and Minefield. I am under the impression that Yahoo! is working on the problem on their end, but not very seriously as I wrote an error message and complaint over a month ago...
relnote for beta 1. fix is external dependent
Darren or Kevin, have either of you been able to investigate this further? Even though it's relnoted, there are a LOT of people complaining about this, including CNet's Stephen Shankland: http://www.news.com/underexposed/8301-13580_3-9820775-39.html Yes, people should be reading relnotes, but it's been a couple weeks since we heard anything from the Yahoo guys on this one. cl
Chris/Tony, As I mentioned in a previous comment, all of the NS_ERROR_DOM_WRONG_DOCUMENT_ERR errors have been fixed in the Y! Mail trunk build (i can launch the beta from my dev build without problems.). This fix however, is *not* in production. It will be incorporated into our next release which will be rolling out sometime Q1. thx, - darren
Thanks Darren. It wasn't clear from your earlier comment whether that was the case or not, but I'm glad to hear you guys have it fixed on your end and will be rolling the fix out soonish (probably around the same timeframe that Firefox 3 will be shipping, as I understand it). cl
Target Milestone: April, per comment 32.
so 'around' April is when FF2 will be shipping or when Y! Mail will have the next release to fix the errors or both?
April would be the end of Q1, so per comment 32, this should be fixed on Yahoo's end by then. Last I heard (June 2007; I can't seem to find an up-to-date roadmap anywhere on mozilla.org), Firefox 3 was planned for "early 2008", which might mean that Yahoo has this fixed before Firefox 3 ships.
(In reply to comment #12) > note: this affect not only paying user from Yahoo, this affects also users in > germany of the free service, since we don`t have the exact same premium system > here with yahoo mail. > Seems to effect paying customers in the UK as well, such as myself.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007120205 Minefield/3.0b2pre Bug still occurs using the laters version of Minefield
Rcvd following error messages trying to get yahoo web mail. Yahoo! Mail experienced a login error: name:NS_ERROR_DOM_WRONG_DOCUMENT_ERR message:Node cannot be used in a document other than the one in which it was created lineNumber:463 Yahoo! Mail experienced a login error: Login error: name:TypeError message:j has no properties lineNumber:648 fileName:http://mail.yimg.com/us.js.yimg.com/combo?/pim/r/dclient/g/js/core/40ed4e2d8d7c4fedfd40ff2da621022e_1.js&/pim/r/dclient/g/js/launch/8f7e5aa4beb78311833eddc3334a14e5_1.js I can get in with Flock which I must do.
10 years ago
Andreas, Vern, and others: This bug will not go away until Yahoo rolls out the next version of their Mail web application.
I haven't seen this problem anymore for about a week. Maybe the changes on their side were rolled out already?
This still repros for me on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b2) Gecko/2007121014 Firefox/3.0b2. dont think its fixed yet.
Still happens with beta2.
Yes because the fix has to be done by Yahoo. They have it fixed internally but have no rolled out this change to their live site. There is nothing that Mozilla can do here.
This bug is very annoying, as everytime I need to use my Y! Mail account I have to wait that the Y! servers realizes that I can't access the new version and asks me if I want to try with the old version. Is there a way I can force Y! Mail to open in the old version? Or I can tell Firefox to open the old one?
(In reply to comment #55) > This bug is very annoying, as everytime I need to use my Y! Mail account I have > to wait that the Y! servers realizes that I can't access the new version and > asks me if I want to try with the old version. > > Is there a way I can force Y! Mail to open in the old version? Or I can tell > Firefox to open the old one? > you can try this after the NS_ERROR_DOM_WRONG_DOCUMENT_ERR error dialog box: 1. click "Trouble logging in?" link at the upper left corner beside the yahoo mail logo. 2. on the "Trouble logging in?" page, click "Switch back to Yahoo! Mail Classic by opting out of Yahoo! Mail" now next time you login, yahoo mail will now be open in the classic mode. to switch back to the new yahoo mail just click "All-New Mail" link at the upper right corner (of your yahoo mail classic) screen.
> now next time you login, yahoo mail will now be open in the classic mode. It doesn't work, it keeps on going to the new version every time I login. For the time being I solved the problem using IE, let's hope that the Y! guys fix the problem soon.
Darren is not with Y! anymore. I am adding my self to CC list and just wanted to let you know that we have fixed these issue and just waiting to roll them out. Thank you for your patience.
Darren is not with Y! anymore. I am adding myself to CC list and just wanted to let you know that we have fixed these issue and just waiting to roll them out. Thank you for your patience.
This bug still exists as of 22 January 2008. I have Fire Fox 3.0b2. I am assuming comment 62 refers to the next beta release.
No; comment 62 refers to Yahoo's mail interface. There is no need to comment in this bug unless you are working at Yahoo and informing the Mozilla community that the fixes are live, at which point the bug can be RESOLVED FIXED.
also for me for yahoo mail box appears this strange error, and with the stable firefox 126.96.36.199 there aren't any problems
If the error mentions NS like it did, it might be a Cocoa issue on Mac OS X. (The NS comes from NeXTSTEP, the predecessor to OS X.)
maybe it's just me, but for some reason, the 'new' yahoo mail is working for me using F3B2
Working for me now also.
Might have to wait a few days/a week until they roll it out to all servers though so don't comment unless this still is not working for you after a week or two.
I'm the product manager for the all new Yahoo! Mail. The latest build we began rolling out last week fixes this bug (hooray!) and adds FF3 to the list of browsers we support on both Windows/Mac. It will take another couple weeks before all users have this new version, but for those who are able to log in now, feel free to verify the fix and mark this bug as close. Thanks, Chris
@Chris Lee, Thank you for telling us, and I can confirm its not out yet. I still get the NS Error and the freeze up and lock out. I'll keep checking though as what I've seen of the beta looks good.
I have the new build of Yahoo mail and it works fine with beta 2, however, after updating to beta 3 today, I noticed that some of the chat contact names (not all) are blank (only the yellow circle is visible). I need to take the mouse cursor over the blank area next to the yellow online icon to bring up tooltip to see the name of the contact.
I just downloaded and installef beta3 for windows (14.45 pm on GMT+2) and unfortunately I have to agree with the rest of the commentators, I get the NS_ERROR too along with the Login Error as was previously stated e.g. on comment #43 so I took action and after I got the pop up message that stated that "Mail took longer to load" I switched to Mail Classic. Is this behaviour something that must be alleviated from Yahoo!'s end or from Mozilla's? Thank you in advance. P.S. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
Read comment 32 and comment 73
(In reply to comment #76) > I have the new build of Yahoo mail and it works fine with beta 2, however, > after updating to beta 3 today, I noticed that some of the chat contact names > (not all) are blank (only the yellow circle is visible). I need to take the > mouse cursor over the blank area next to the yellow online icon to bring up > tooltip to see the name of the contact. > Can confirm this affects me too, only since installing Fx b3; however, with Fx b2 Yahoo! Mail didn't work at all, so this is a massive improvement (presumably from the Y! side).
Comment 76 and comment 81 should be filed as a separate bug (one or the other of you; don't both file it, please), as it really has nothing whatsoever to do with this one. cl
I can also confirm that the changes have reached the server I happen to be using. However, now that Firefox 3 can open Yahoo Mail "beta" without problems, a more serious problem has shown up: FF crashes extremely frequently on Yahoo Mail. So frquently that it's not usable. See bug 419695. I hope Chris Lee will take a note of this.
Roman, do you have Firebug installed? that causes a lot of crashes on the new yahoo mail.
Also Roman, from your bug 419695 it looks like you are not even using one of the released betas. You are using Minefield (dont know how old). why dont you try firefox 3 beta 3 too?
Manuel, I do have Firebug installed, but: - it is disabled; - and it's installed only in my "old" profile, and crashes happen in my new, clean profile that I created for some version of beta 4 pre. Minefield I am using is of the latest version (I use nightly builds). However, I will try beta 3. That's a good point.
I meant to say that crashes happen in my new profile *too*.
Well, I just tried beta 3 and saw *this* bug is still there for me. So, it seems to be happening is that later versions of Firefox 3 beta have managed to hide this particular bug and led to crashes. I hope when changes made by Yahoo devs propagate to my account, behavior described in this bug and the crashes will disappear. Perhaps, my bug 419695 will be useful to FF developers anyway.
Roman - Please try uninstalling Firebug all together and then see if Mail is still crashing for you on Beta 3. This release has not be pushed out to all users yet. We are in the process of wrapping that up this week. Assuming no major issues, the majority of users should have the latest build by early next week.
Roman R. Please file a new bug. This bug is closed and your bug has nothing at all to do with this one. Reply back with the new bug number and leave this one as is. Thanks
Kurt, I have filed a new bug report and posted it here, in comment #87. Also, as I've learned after I filed that bug report, the problem I described here does have something to do with this bug because Firefox has changed how they treat what the old code of Yahoo Mail did that caused you to file this bug. (See bug 418755.)
Marking this bug verified on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4pre) Gecko/2008022604 Minefield/3.0b4pre. Thanks yahoo team for fixing this!
(In reply to comment #95) > Kurt, I have filed a new bug report and posted it here, in comment #87. > Also, as I've learned after I filed that bug report, the problem I described > here does have something to do with this bug because Firefox has changed how > they treat what the old code of Yahoo Mail did that caused you to file this > bug. (See bug 418755.) Ok, well either way this bug was opened for a specific reason and has been fixed. And now it even looks like WRONG_DOCUMENT_ERR won't even be thrown anymore anyways since it seems that it is to hard to get people to write according to standards so some devs just wanted to stop trying to push it. Anyways, this bug is even now verified fixed for the original issue that started this bug so leave it be.
Chris, I did what you asked. However, let's talk in bug 419695 to avoid agitating people here.
Nael, if you read comments starting from #87, you will understand what's going on. As Chris said, the new code "has not be pushed out to all users yet." The reason you can use Yahoo Mail with b4pre is that Firefox no longer objects to the way Yahoo Mail uses it.
Chris, if at all possible, please delay rolling out changes on your side until Mozilla devs get a handle on why FF crashes on Yahoo Mail (as reported in bug 419695). Right now I can easily reproduce the bug, and they are debugging FF on my machine remotely. It would be a bad thing, if your changes hide the cause of the crashes. Thanks.
Confirmed for the mail.yahoo.com on the fully patched Ubuntu 8.04 - the Hardy Heron Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Confirmed for the site https://www.bloglines.com $ firefox (firefox:13122): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup. (firefox:13122): atk-bridge-WARNING **: IOR not set. (firefox:13122): atk-bridge-WARNING **: Could not locate registry Segmentation fault $
Created attachment 328444 [details] run firefox -safe-mode Continue "Confirmed for bloglines.com" I attached what firefox dumps when i run firefox -safe-mode from the command line
(In reply to comment #103) > Confirmed for the site https://www.bloglines.com That should be filed as its own bug if it is, indeed, a bug. It's not at all clear whether "confirmed" in comment 103 means "this bug exists" or "this bug is fixed". Either way, if you see new instances of this bug, you should file them as new bugs, because *this* bug has been fixed for several months.
I am sorry, i did not pay attention that the issue is marked fixed. Yesterday i discovered that firefox crashes when visiting Yahoo Mail. search brought me eventually to this bug record. i do the same routine daily - yahoo mail, gmail, bloglines. Bloglines crashed the firefox too. there was no problem two days ago and the problem appeared only about 12 hours ago. i do not know if the problem is a different and new one or this is the same already fixed problem. i am going to open a new issue for the bloglines. (In reply to comment #105) > (In reply to comment #103) > > > Confirmed for the site https://www.bloglines.com > That should be filed as its own bug if it is, indeed, a bug. It's not at all > clear whether "confirmed" in comment 103 means "this bug exists" or "this bug > is fixed". Either way, if you see new instances of this bug, you should file > them as new bugs, because *this* bug has been fixed for several months. >