361709 - Yahoo Mail Beta Login error: Node cannot be used in a document other than the one in which it was created

Status: RESOLVED FIXED

(Tech Evangelism Graveyard :: English US, defect)

Description

[-fullmetaljacket-]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a1) Gecko/20061122 Minefield/3.0a1
Build Identifier: 

after log in into the yahoo mail beta, the following error popup:

"Yahoo Mail Beta experienced a login error:Login error: Node cannot be used in a document other than the one in which it was created"

work fine with
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a1) Gecko/20061122 Minefield/3.0a1 ID:2006112204 [cairo]

but no longer work with
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a1) Gecko/20061122 Minefield/3.0a1 ID:2006112300 [cairo]

Reproducible: Always

Comment 1

[Bill Gianopoulos [:WG9s]]

Confirming.

Regression from check-in for bug 47903 (although it may be that Yahoo is doing something they should not be here).

Comment 2

[Peter Van der Beken [:peterv]]

We're following the DOM spec more closely, so it'd be preferable to get Yahoo to fix this.

Comment 3

[Bill Gianopoulos [:WG9s]]

(In reply to comment #2)
> We're following the DOM spec more closely, so it'd be preferable to get Yahoo
> to fix this.
> 
Well, unless the code for bug 47903 gets checked into the branch, I am sure we are months away from Yahoo doing anything to fix this.  There stance will be like everyone elses:

  "We do not guarantee our site will work with Alpha or Beta browsers!"

So, when this does become an issue when Firefox 3 is released it the new Yahoo mail will be production and not beta.

I suppose I am just stating the obvious here.

Comment 4

[Boris Zbarsky [:bzbarsky]]

I thought we had technical contacts at yahoo mail that we could talk to about this... shaver, do you happen to know who they are or who would know about them?

Comment 5

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

I think chofmann's the man with this plan.

Comment 6

[Ratan Hudda]

we are investigating it and feel free to contact me if you have any questions.

Comment 7

[Kevin Johnston]

We at Yahoo have analyzed the problem and are willing to fix this in our code (we in fact wondered a long time ago why this was not enforced) but I would like  to point out that this may cause more web breakage than Mozilla.org is currently expecting.

The Mail Beta code in question is cross-platform and does not fail on IE 6/7.  The test case https://bugzilla.mozilla.org/attachment.cgi?id=214886, in bug 47903, named "Testcase", should not be considered as useful for determining whether or not the Gecko bugfix is break-causing.  That test creates and transfers nodes between HTML documents, which is not something we ever do.

The action that broke us involves transferring nodes among XML documents-- chiefly, take the documentElement or its children from an XHR response, and stitch it into a local store with other data.  This operation throws no errors on IE 6/7 and I suspect it is a more real-world-representative test case than "Testcase."

So far as I know any XML-to-XMLDocument node transfer works with no errors in IE-- it kind of has to, as importNode is not even widely exposed in current IE.  It's just newly available in MSXML6 with Vista, AFAIK.  Again, we don't object to fixing this, but don't let "Testcase" fill you with false confidence.

Comment 8

[Peter Van der Beken [:peterv]]

Need to figure out what exactly IE is doing.

(In reply to comment #7)
> The Mail Beta code in question is cross-platform and does not fail on IE 6/7.

What about Opera and Safari?

> Again, we don't object
> to fixing this, but don't let "Testcase" fill you with false confidence.

I don't think we were ever confident that this would be simple ;-).

Comment 9

[Martijn Wargers (dead)]

*** Bug 362964 has been marked as a duplicate of this bug. ***

Comment 10

[Jesse Ruderman]

*** Bug 363047 has been marked as a duplicate of this bug. ***

Comment 11

[Kent Paul Dolan]

This bug also occurs with SeaMonkey as of Build 2006121709 (at least),
built for MS-Windows XP, is "fixed" by reversion to SeaMonkey 20061120xx
(at least), does not occur in IE 6.0.

Can someone let me know by email where by URL to find the SeaMonkey
nightly build next before the bug-fix check-in that caused this
breakage?

I want to stay as "close to current as possible" with nightlies, but
this bug is lethal breakage to my day to day SeaMonkey browser use.

[Using IE every time I want to read email just makes my skin crawl.
Worse yet is that Microsoft's update mechanism is trying daily to
force its bugfest IE 7.0 browser into my computer.]

xanthian.

Comment 12

[u88484]

Fixed in a recent yahoo mail beta update.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20061219 Minefield/3.0a2pre

Comment 13

[Bill Gianopoulos [:WG9s]]

This does NOT work for me with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20061221 Minefield/3.0a2pre ID:2006122104 [cairo].  I even tried clearing my cache first.

I suppose it is possible, however, that Yahoo is in the process of fixing the issue on their end and the fix is just not universally deployed on their servers.

REOPENING

Comment 14

[u88484]

Attachment: Screenshot of Y! Mail beta working in recent trunk

Comment 15

[Marcus Beckmann]

not working here using:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20061221 Minefield/3.0a2pre ID:2006122100 [cairo]

cheers
mbb

Comment 16

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Has anyone tried the yahoo mail BETA and have it fail? Or are you just failing in the deployed current version (which is sounds like does not have the fix yet)

Comment 17

[Bill Gianopoulos [:WG9s]]

The deployed current version works fine.  It is the deployed beta version that fails.  I know of no other beta version.  Do they now have 2 beta versions you can somehow chose between?

Comment 18

[u88484]

(In reply to comment #17)
> The deployed current version works fine.  It is the deployed beta version that
> fails.  I know of no other beta version.  Do they now have 2 beta versions you
> can somehow chose between?
> 

There was never an issue with the regular yahoo mail. It's always been the beta that didn't work. If you look in my screenshot in the title bar you'll see that it is the beta that I'm using and working with a recent build and now even today's build

Comment 19

[Bill Gianopoulos [:WG9s]]

It appears the remaining issue here is getting the new beta code deployed to all of the yahoo mail server (they have a a lot of them) it appears from previous comments that it is working on f308.  but my email appears to be on f566 where it does not.  We should leave this bug open until it either someone fror\m yahoo comments on this bug that all the servers have been updated or at least until it works for most people to avoid getting more duplicate bugs.

Comment 20

[Marcus Beckmann]

it is also not working on f268 ....

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20061221 Minefield/3.0a2pre ID:2006122100 [cairo]

Comment 21

[Ratan Hudda]

We have fixed it on mail side but it will be available from next realease once it is deployed on all servers. Looks like fix is already available to some users.

Comment 22

[kookykrazee]

I am using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a2pre) Gecko/20061223 Minefield/3.0a2pre and have yahoo server f319 which appears to still not be updated, as of yet.  Same error and same problem and before.

Comment 23

[kookykrazee]

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a2pre) Gecko/20061227 Minefield/3.0a2pre still not working on f319.

Comment 24

[-fullmetaljacket-]

(In reply to comment #21)
> We have fixed it on mail side but it will be available from next realease once
> it is deployed on all servers. Looks like fix is already available to some
> users.
> 

thanks for fixing this.

when will the ETA of the fixes for this to land on all of your servers?

Comment 25

[Ratan Hudda]

The fix should be on all servers by first week of Feb, most users will have it by 3rd week of Jan.

Comment 26

[Joao Eiras]

> What about Opera and Safari?

I don't know about Safari, but Opera in some 9.0* version changed their DOM implementation, against the specification, to implicitly call adoptNode for each method that might exchange nodes between different documents. This was announced at w3c www-dom.
This was the workaround they did for all the problematic website relying on Mozilla behaviour. When the first public build of Mozilla that fixes this problem is released, Opera will revert their behaviour to what's specified.

@ the yahoo folks: thanks for the fix.

Comment 27

[Boris Zbarsky [:bzbarsky]]

Safari is in the same situation as Opera, last I checked.

Comment 28

[Nigel L]

And Konqueror has an even worse problem, getting utterly stuck without the option of using Y!Mail "classic" after the initial, ill-advised response to "Hmmmm, your browser isn't officially supported."
Anyway, thanks to Ratan Hudda and the others who took heed.  Heck, Y!Mail is cool!

Comment 29

[-fullmetaljacket-]

marking this FIXED as per comment #25 and since it was already march 1 at this part of the world.

Comment 30

[Bob Clary [:bc] (inactive)]

I saw this today in Minefield:
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:512

Comment 31

[-fullmetaljacket-]

new bug is bug# 398381

im closing this one.