Bug 19365 - <object> element with attribute usemap do not provide client-side image map functionality
Summary: <object> element with attribute usemap do not provide client-side image map f...
Status: RESOLVED DUPLICATE of bug 15032
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 525.x (Safari 3.1)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL: http://haignet.co.uk/object-image-map...
Depends on:
Reported: 2008-06-02 18:07 PDT by Gérard Talbot
Modified: 2010-11-05 12:57 PDT (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Gérard Talbot 2008-06-02 18:07:51 PDT
This bug spun from bug 15032.

Opera 9.26, Opera 9.50, Firefox 3 RC1 rv:1.9 build 2008051206, Seamonkey 2.0a1 all pass all 4 example-tests in the provided URL's webpage from Chris Haig.

Explorer 8 beta 1 passes example-test 1.2.

Safari 3.1.1 build 525.17.0 fails all 4 example-tests.

Note that example-test 2.2 at
fails just because of bug 5566

Other related/worth-mentioning issues:

HTML 4 and HTML 5 both have usemap as an attribute for <object>s:




Another testcase on <object> and image map:

Note: I chose Component: HTML DOM but it could be Component: Images instead.

+CC Robert Burns
Comment 1 Gérard Talbot 2009-06-14 10:47:16 PDT
References update:

HTML 4 and HTML 5 both have usemap as an attribute for the HTML object element:


The usemap attribute, if present while the object element represents an image, can indicate that the object has an associated image map. The attribute must be ignored if the object element doesn't represent an image.


Connect IE beta feedback bug report (id 333636):
Image map reference fails if called using the <object> element

Internet Explorer 8 passes this test:

regards, Gérard
Comment 2 Gérard Talbot 2009-06-14 11:12:59 PDT
Example-tests 1.2 and 2.2 coming from
now PASS in latest stable release Safari 4.0 build 530.17

regards, Gérard
Comment 3 Darin Adler 2010-11-05 12:57:00 PDT

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