Closed Bug 1427 Opened 26 years ago Closed 25 years ago

Image maps areas not accessible as content through DOM

Categories

(Core :: Layout, defect, P2)

x86
Windows NT
defect

Tracking

()

VERIFIED DUPLICATE of bug 9140

People

(Reporter: jcarpenter0524, Assigned: joki)

References

()

Details

NT4.0 11/18 build viewer & xpviewer - Go to URL: http://www.imdb.com - top row of images [SEARCH], [INDEX], etc are an image map, but you can't click the options. - clicking where the cursor is supposed to turn to a hand does not work - Go to URL: http://www.amazon.com - click on any option (Book Search, Browse Subjects, etc.) and get msg: "Imagemap Error Your client did not send any coordinates. Either your client doesn't support imagemap or the map file was not accessed as a map."
Status: NEW → ASSIGNED
Assignee: troy → joki
Status: ASSIGNED → NEW
Priority: P2 → P1
Tom, the problem is that both HandleEvent() and GetCursor() are being called with the "point" not having been translated into the frame's local coordinate space. I added some temporary code to HandleEvent() and GetCursor() (nsImageFrame.cpp) to temporarily workaround this problem. You'll need to remove it once it's fixed
Status: NEW → ASSIGNED
Priority: P1 → P2
Summary: Image maps are not clickable → Image maps areas not accessible as content through DOM
Changing the title on this one. The main problem with imagemaps now is that we have to hook up the content objects for the map areas and get rid of the current areas stuff. Not sure if it'll be me that deals with this eventually but I'll hold onto this for now. Other than that these work for now.
Setting all current Open Critical and Major to M3
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Status: ASSIGNED → NEW
Target Milestone: M3 → M5
Target Milestone: M5 → M6
Moving out to M7
Target Milestone: M7 → M9
*** Bug 7759 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Target Milestone: M9 → M11
Moving to M11
Is this critical for beta? If not, lets push it out.
Brendan, would you count this as new functionality to be pushed out beyond beta?
Moving multiple bugs to m12
[monitoring AREA element bugs]
Moving to m13 because Joki seems to be distracted.
Target Milestone: M13 → M14
Moving M14.
*** This bug has been marked as a duplicate of 9140 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Marking as verified dup of 9140.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.