369615 - Menus don't expand anymore on http://www.parapsy.nl/

Status: RESOLVED FIXED

(Tech Evangelism Graveyard :: Dutch, defect)

Description

[Ria Klaassen (not reading all bugmail)]

Steps to reproduce:

- Go to http://www.parapsy.nl/
- Hover over the menus on top 

Result: they don't expand anymore
An error is present in the error console:

Error: uncaught exception: [Exception... "Node cannot be used in a document other than the one in which it was created"  code: "4" nsresult: "0x80530004 (NS_ERROR_DOM_WRONG_DOCUMENT_ERR)"  location: "http://www.parapsy.nl/coolmenus3.js Line: 343"]

Regression between 2006-11-22:09 and 2006-11-22:11:
http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=2006-11-22+08%3A00&maxdate=2006-11-22+12%3A00

The error seems to point to Bug 47903

Comment 1

[Patrick]

If i remember correctly Coolmenus3 doesn't work correctly with firefox (browser checking error), unsure if this works with Gecko at all. Also unsure about why it worked for you previously. Maybe firefox got an updated user agent string in the regression window you found?

Contact person for the site is fred at melssen.nl
I'll drop him a line later today.

Comment 2

[Ria Klaassen (not reading all bugmail)]

Works fine in branch.

Comment 3

[Patrick]

(In reply to comment #2)
> Works fine in branch.

then this can't be a Tech Evang issue i guess

Comment 4

[Patrick]

Re-assigning per comment 3

Comment 5

[Jesse Ruderman]

> Works fine in branch, [so] this can't be a Tech Evang issue i guess

Bug 47903 was an intentional bug trunk-only change, so this can still be Tech Evang.

Comment 6

[:Gavin Sharp [email: [e-mail]]]

Yeah, this is still a tech evang issue. Even if it wasn't, it certainly isn't a Firefox::General bug. Please use Core::General for bugs like this in the future.

Comment 7

[Jesse Ruderman]

(Or even Core::DOM.)

Comment 8

[Patrick]

(In reply to comment #7)
> (Or even Core::DOM.)
> 

That's why i used General since it was not obvious to me [or others ;)] which specific category would fit best. Anyhoo, it was my understanding that in principle changes in Gecko couldn't be related to Tech Evang bugs, as Tech Evang bugs more or less per definition are not related to changes in the Moz code base.

But i guess that making us more compliant can actually break compatibility with certain site.

Message to web master sent.

Comment 9

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #8)
> That's why i used General since it was not obvious to me [or others ;)] which
> specific category would fit best.

Sure, but you still used the wrong Product. Core::General and Firefox::General are not the same thing.

> Anyhoo, it was my understanding that in principle changes in Gecko couldn't be
> related to Tech Evang bugs, as Tech Evang bugs more or less per definition are
> not related to changes in the Moz code base.

That's not my definition of "Tech Evang" :). In this case the decision was made to break specific cases that used to work. It was expected that some sites would need to adjust their code accordingly, and filing Tech Evangelism bugs can help make that happen.

Comment 10

[Patrick]

(In reply to comment #9)
> Sure, but you still used the wrong Product. Core::General and Firefox::General
> are not the same thing.

Darn, you're right. Remind me not to re-assign bugs after a dreadful day at work :( 
 
> That's not my definition of "Tech Evang" :). In this case the decision was made
> to break specific cases that used to work. It was expected that some sites
> would need to adjust their code accordingly, and filing Tech Evangelism bugs
> can help make that happen.

Good point, as i realized in comment 8 that we can actually break certain sites with code changes from our end.

Anyway, first e-mail bounced. New e-mail sent to info at parapsy.nl 

Comment 11

[Ria Klaassen (not reading all bugmail)]

The menus are still broken in the latest trunk build.

Comment 12

[Biju]

looks like it is working now

Comment 13

[Ria Klaassen (not reading all bugmail)]

Thanks for testing Biju. This was indeed fixed by some checkin in February 2008.
As I don't know exactly what bug fixed this, resolving WFM.

Comment 14

[Biju]

(In reply to comment #13)
> As I don't know exactly what bug fixed this, resolving WFM.

Fixed by bug 418755. Marking FIXED.