66342 - Bad links have a very lengthy context-sensitive menu!

Status: VERIFIED DUPLICATE of bug 62744

(Core :: XUL, defect)

Description

[Christos Cheretakis]

The page I used to get the described result is password protected, but I guess
it works with any page that contains code like this:

<a href="htt://users.tninet.se/~odc669k/video
">htt://users.tninet.se/~odc669k/video
</a>

Right-clicking with the mouse on the link produces a very lengthy menu. The menu
contains all the normal options, plus any option relevant ro frames, altough the
page is not contained inside frames.

While I was switching windows writing this bug report, and clicking & selecting
on the page, the menu became suddenly correct!

Testing with 2001011808 on linux

I'm sure I will be able to reproduce it now. I will give more precise steps next
time.
Is there any way to capture a menu?

Comment 1

[Mike Pinkerton (not reading bugmail)]

content not toolkit.

Comment 2

[Christos Cheretakis]

When menu is opening, mozilla says on its console:

line 0: uncaught exception, [Exception <no message>, code = -2142568430 nsresult
= 0x804b0012 location = chrome://communicator/content/nsContextMenu.js Line 358]

Comment 3

[Christos Cheretakis]

Attachment: Screenshot of the menu. was able to reproduce

Comment 4

[Christos Cheretakis]

On the console as well:

JavaScript:
line 0: contextMenu has no properties

Comment 5

[John Morrison]

In the end, this is the same "!link.protocol" exception as bug 62744, which 
just needs a try/catch, I suppose.

*** This bug has been marked as a duplicate of 62744 ***

Comment 6

[John Morrison]

verified.

Comment 7

[Christos Cheretakis]

Don't think this is a duplicate of 62744
...

Comment 8

[Bill Law]

I think there's a bug in the DOM.

<a href="foo:bar">

may not be really good HTML, but I don't think the resulting DOM should have a
Link object whose protocol property throws a JS exception when you access it.

Of course, we could catch that bogus exception and cover up the mistake, but my
suspicion is we'll get burned by the same bogus JS/DOM behavior again at some
point.  Better to fix the problem at its source.\

I've tweaked the URL in this bug so that it will exhibit this behavior (not sure
it will work, though).

I think this is the same bug as 62744 (although I'm not sure what makes that
bug's Link objects go bad).