83883 - <input type="image"> has wrong context menu on Win32.

Status: RESOLVED DUPLICATE of bug 77122

(Core :: XUL, defect, P2)

Description

[K Chayka]

win32 talkback build 2001060120, win98se

Go to the above link, or display any other map at the www.mapquest.com site.
Right click on the map image. No context menu displays, so the map (gif) can be
saved, displayed in a separate window, whatever. Like it's not even recognized
as an image. Can right-click/save the map image in Netscape 6 no problem.

Comment 1

[Chris Brien]

Attachment: Shows an <input type="image"> which has no context menu

Comment 2

[Chris Brien]

The image is actually an <input type="image"> element rather than a simpler
<img>, which is why the context menu doesn't appear.
The component should probably be HTML form controls.
See my attached testcase.

Comment 3

[John Morrison]

So, this regressed (context menu stopped coming up at all when over an <input 
type=image>) between 5/25 am and 5/27 am. I put some dump statements in 
nsContextMenu.js, and can see that the setTarget method is being called, so
at least the initial application setup is working. 

[I noticed that either before or after the 25th, .setTarget() is actually
called three times, twice for the <input type=image> and once with a browser
element [which overwrites the value of this.onImage, and means that no image
options are set for the context menu (see bug 77122) and frameset options are
set]].

Giving this to dr for now. Can you just see which side of the line the 
problem lies (app logic or something with the popup or events). There may be 
some interest in fixing this from Netscape's point of view, since this is 
MapQuest.

Comment 4

[Doron Rosenberg (IBM)]

linux cvs from yesterday, this works (both the url and testcase)

Comment 5

[Dan Rosen]

worksforme too. is there anybody with an up to date tree for whom this still
doesn't work?

Comment 6

[John Morrison]

Yeah, me. Doesn't work on win32. But, whatever. Minor platform.

Comment 7

[Dan Rosen]

So this is windows-only, eh... Ok, 0.9.3. I guess we can see if this can make it
into 0.9.2 when the time comes.

Comment 8

[Dan Rosen]

[spam] -> 0.9.5

Comment 9

[Dan Rosen]

[spam] [e-mail]'s bugs subject to redistribution by chofmann. R!

Comment 10

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Lemme have a look, I fixed some other context menus bugs just recently...

Comment 11

[John Morrison]

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

Comment 12

[John Morrison]

Okay, the context menu shows in current builds on windows, but the items in 
the menu are wrong (e.g., says 'Open frame in new window', 'Show Frame Source'
for the testcase attachment 36967 [details], and does not offer, e.g., 'Copy Link 
Location').

So strange that this is only on windows, though. [Linux/Mac are OK.]

Comment 13

[Boris Zbarsky [:bzbarsky]]

This is now just a duplicate of bug 77122, no?

Comment 14

[John Morrison]

I suppose it is a duplicate, but perhaps heikki has an idea of what is wrong
here

Comment 15

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Yeah, sure does look like a dupe.

I looked all the places that used to be the cause of problems with context menus
(as far as I could tell) but did not find anything that could cause this bug.

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