Open Bug 25199 Opened 25 years ago Updated 2 years ago

Opening an imagemap link in a new window/tab doesn't send coordinates

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect, P3)

Desktop
All
defect

Tracking

()

Future

People

(Reporter: S.D.deHoog, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: relnote, testcase, Whiteboard: [nsbeta2-][nsbeta3-])

Attachments

(3 files)

When clicking on an imagemap, the coordinates get sent as part of the URL. However, selecting 'open in new window' from the context menu does not. For example: left-clicking goes to imgmaptest.html?xpos,ypos right-clicking goes to imgmaptest.html Expected behaviour: include the coordinates when opening in a new window the same way left-clicking does.
Attached file Simple HTML file with imagemap (deleted) —
Attached image and an image to test it with... (deleted) —
Eric: Do you know who handles image maps in layout land? -p
Assignee: pnunn → pollmann
Well, imagemaps are definitely handled in layout land (nsImageMapFrame.cpp or somesuch). I think Kipp was the one who implemented these, but last I heard nobody owned them. I'll take this bug for now but it may not get fixed for a while (my buglist, ack, is huge).
Status: NEW → ASSIGNED
Component: ImageLib → Layout
Target Milestone: M17
QA Assigning to Mr. Peterson, who is now handling image maps.
QA Contact: elig → petersen
Rescheduling
Target Milestone: M17 → M20
Nom. nsbeta2, recc. nsbeta2+. This is basic HTML 3.2, and image maps are widely used for navigation, and we aren't passing the URL between windows correctly. Very bad Basic Browser Correctness issue. HTML 3.2 is key b2 criterion.
Keywords: nsbeta2
Putting on [nsbeta2-] radar. Not critical to beta2. But adding to nsbeta3 keyword radar to get a fix in before rtm.
Keywords: nsbeta3
Whiteboard: [nsbeta2-]
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: M20 → Future
Marking nsbeta3-
Keywords: relnote
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3-]
It seems unclear to me whether this bug requires either of a "developer" or "user" release note. If anyone feels it does, can they please draft one and then nominate with the relnote-user or relnote-rtm strings in the Status Whiteboard. Thanks :-) Gerv
Upon managerial request, adding the "testcase" keyword to 84 open layout bugs that do not have the "testcase" keyword and yet have an attachement with the word "test" in the description field. Apologies for any mistakes.
Keywords: testcase
Attached file testcase of Washington Tech image map (deleted) —
I added a testcase taken from HTML on the Washington Tech website. I first saw it on this article: http://www.washtech.com/news/media/11421-1.html It appears that the right-click only looks at the A href instead of the ismap information in the Img tag. Adding Mozilla1.0 and 4xp keywords (Netscape 4.x does not exhibit this problem).
Keywords: 4xp, mozilla1.0
Bug 82826 says opening in a new window by middle-clicking also fails. Should it be a duplicate? Ctrl+click on build 2001072503 behaves strangely. The new window opens and shows the url without the coordinates, but the click apparently also goes to the original window and shows the proper results (using the coordinates) in the original window.
Bulk reassigning form bugs to Alex
Assignee: pollmann → alexsavulov
Status: ASSIGNED → NEW
*** Bug 82826 has been marked as a duplicate of this bug. ***
82826 was assigned to joki and 097 targeted. Happening for tabs too.
OS: Windows NT → All
Hardware: PC → All
Summary: Opening an imagemap link in a new window doesn't send coordinates → Opening an imagemap link in a new window/tab doesn't send coordinates
More fun with imagemaps and opening new windows: 1. Click on "Show dependency graph" link on this bug in Bugzilla. 2. Right-click, select "Open in new window" (or middle-click) on the imagemap. 3. Note that source for imagemap is returned from webdot.cgi on www.research.att.com. Fun stuff.
Blocks: 152489
*** Bug 152489 has been marked as a duplicate of this bug. ***
Flags: blocking1.3?
Flags: blocking1.3? → blocking1.3-
The problem is merely that of getting the click coords in the coordinate system of the image. Unfortunately, that's a pretty hard problem (since there is no real way, from where the new window/tab code lives, to determine where the image is located in the viewport or document). I suppose we could add an interface to events that would not have classinfo and would report the coords in the target frame (whatever that means in general).
Isn't this a question of how we dispatch links? Shouldn't we resolve server-side image maps in a layer before we separate open-in-new-window from normal open?
Assignee: alexsavulov → other
QA Contact: petersen → ian
"open in new window/tab" are hooked up in the UI itself (in nsContextMenu.js). They basically share no code with the normal click codepath....
*** Bug 245863 has been marked as a duplicate of this bug. ***
This has been a cronic problem since the gg with Mozilla. I'm not sure this is the same bug, but successive clicks on an image map will result only in the FIRST set of coords being resent. This problem does not Occur in IE, Opera, or Netscape prior to V5. Dhu
Interestingly enough, both IE7 and Opera 9.02 appear to fail on these testcases as well.
Would probably be fixed by the plan in bug 335963.
Assignee: layout → nobody
Depends on: 335963
QA Contact: ian → layout

This issue still occurs just the same on Windows 10, Ubuntu 20, Mac OS 11.

Hardware: All → Desktop
Severity: major → S4
Component: Layout → Layout: Images, Video, and HTML Frames

Notes on various ways to open-in-new-tab:
A) Ctrl+Click adds the coordinates the current tab's URL (rather than the one in the new tab).
B) Middle-click doesn't put the coordinates in either URL.
C) Right-click + open-in-new-tab doesn't put the coordinates in either URL.

Chrome puts the coordinates in the new tab's URL (as-expected, I think?) for (A) and (B), but they match us for (C) with the context-menu (no coordinates).

Anyway: seems like an interesting behavioral difference still, but pretty low-severity.

The severity field for this bug is relatively low, S4. However, the bug has 3 duplicates.
:emilio, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(emilio)

Imagemaps aren't so wildly used nowadays, S4 seems reasonable.

Flags: needinfo?(emilio)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: