Closed Bug 163928 Opened 23 years ago Closed 23 years ago

Particular linked image doesn't show context menu

Categories

(Core :: DOM: Navigation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: mikepinkerton, Assigned: ccarlen)

References

()

Details

(Keywords: topembed)

- go to www.macinmind.com in MFCEmbed - rightclick on any of the images on the leftside image nav bar expected: - link-image context menu should appear actual: - nothing Here's what is going on: - we get into the context menu code in the ContextMenuListener attached to the DocShellTreeRoot. It notices the <A> tag and that it has an HREF so it correctly sets the flag that it's a link. It then calls into the embedding app to show the context menu. - w/in the embedding app (MFCEmbed or PPEmbed), the code tries to find something that will QI to nsIDOMHTMLAnchorElement. however, it can't, and walks all the way to the top and then bails w/out showing the menu. - PPEmbed will show the menu, but trying to open the link will go through similar code and fail. There's something about this particular image link that just won't cast to nsIDOMHTMLAnchorElement and it's throwing off all our embedding apps.
saari, this is a bug for what we talked about in the meeting.
Keywords: topembed
*** This bug has been marked as a duplicate of 33583 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
I'm un-duping this bug because it describes a problem in embedding apps, not mozilla. > - w/in the embedding app (MFCEmbed or PPEmbed), the code tries to find something that will QI to nsIDOMHTMLAnchorElement. however, it can't, and walks all the way to the top and then bails w/out showing the menu. For embedding apps, this is the crux of the issue. I'm working on the context menu handling for embedding apps and it fixes this issue by solving the above problem.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Taking since I have a fix.
Assignee: adamlock → ccarlen
Status: REOPENED → NEW
Fixed by bugscape 8854.
Status: NEW → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.