15032 – An OBJECT element with the attribute usemap does not provide client-side image map functionality

NEW 15032

An OBJECT element with the attribute usemap does not provide client-side image map functionality

https://bugs.webkit.org/show_bug.cgi?id=15032

Summary An OBJECT element with the attribute usemap does not provide client-side imag...

Robert Burns

Reported 2007-08-20 21:39:15 PDT

When the element input uses usemap=IDREF to point to a client-side image map in the same document, WebKit should make use of that image map in several ways. 1) it should map the area elements within the map element to the appropriate coordinates and shapes onto the image for the input element; 2) it should provide tooltips from the area element's title attribute upon mouse-over on those mapped areas; 3) it should treat those areas generally as frames (though not necessarily rectangular frames) with all of the behaviors and methods of those frames, including: a) receive events b) focus outline indicateion c) apply CSS bos model (though not necessarily rectangular) properties including margin, padding, border and outline. d) apply CSS :hover and other pseudo selectors to the frames corresponding to the area elements e) apply other CSS where appropriate Currently WebKit submits a form onclick, but does not provide any of the benefits of the usemap attribute.

Attachments
This demonstrates the different behavior between the client-side image maps when referenced from a INPUT and from and IMG (12.15 KB, application/x-webarchive) 2007-08-21 01:21 PDT, Robert Burns	no flags	Details
This attachment replaces the previous one (13.22 KB, application/x-webarchive) 2007-08-21 04:26 PDT, Robert Burns	no flags	Details
Proposed patch (5.86 KB, patch) 2011-05-15 17:38 PDT, Andreas Kling	no flags	Details Formatted Diff Diff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.

Robert Burns

Comment 1 2007-08-20 21:40:53 PDT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html lang="en"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8" > <title>Untitled</title> <style type='text/css'> input {height: 100px; width: 200px;} #leftarea {border-style: solid; border-color: red; border-size: 1px; } #rightarea {border-style: solid; border-color: blue; border-size: 1px; } img:hover {cursor: crosshair;} input:hover {cursor: wait;} area:hover {cursor: wait;} </style> </head> <body> <p> <map name=m> <area id=leftarea title='left-side' alt='left-side' shape=rect coords='0,0,100,100' > <area id=rightarea title='right-side' alt='right-side' shape=rect coords='100,0,200,100' > </map> <img src='image'> </p> <form onsubmit='alert("submit")' action=.><input type=image src=image usemap='#m'></form> </body> </html>

Maciej Stachowiak

Comment 2 2007-08-21 00:18:59 PDT

This feature is underspecified in HTML4, and not implemented by IE. It is also likely to be dropped in HTML5 and may be removed from Mozilla and Opera as a result.

Alexey Proskuryakov

Comment 3 2007-08-21 00:55:43 PDT

Clearly, breaking compatibility with IE just because of HTML4 spec is not an option for us. This issue is being extensively discussed by the HTML WG right now, so I do not see any reason to rehash the discussion here. Please re-open this bug if HTML5 draft changes to accommodate this feature.

Robert Burns

Comment 4 2007-08-21 01:10:10 PDT

(In reply to comment #3) > Clearly, breaking compatibility with IE just because of HTML4 spec is not an > option for us. This issue is being extensively discussed by the HTML WG right > now, so I do not see any reason to rehash the discussion here. > > Please re-open this bug if HTML5 draft changes to accommodate this feature. This would not break compatibility with IE. The point is to provide greater visual feedback to the user. The form should still be submitted as WebKit already does. The title attribute tooltip is based on the existing recommendations. and brings parity with Firefox and Opera. The other enhancements would not break compatibility with anything else, but would set WebKit above the competing implementations. As for HTML5, by the editors own admission, this is a recommendation that is years away from reaching candidate recommendation status. We cannot wait until then to fix bugs in WebKit or make enhancements. Once it becomes a candidate recommendation, we can consider what changes should happn to WebKit to bring it in line with the new recommendation.

Robert Burns

Comment 5 2007-08-21 01:21:16 PDT

Created attachment 16048 [details] This demonstrates the different behavior between the client-side image maps when referenced from a INPUT and from and IMG

Robert Burns

Comment 6 2007-08-21 01:24:06 PDT

With this latest attachment,I think the bug is clearly demonstrated. The image maps should behave the same with respect to the @title attribute tooltips. The other features mentioned in the bug are properly feature enhancement requests and filed elsewhere. However, the bug as written in the summary should properly be fixed.

Robert Burns

Comment 7 2007-08-21 04:25:14 PDT

I have a new attachment to replace the previous attachment. I think this better illustrates the problem and that it also applies to OBJECT (also the last example had some non-relevant validation errors). Perhaps a succinct way to put this is: Image maps do not enable feedback such as mouseover tooltips and The relevant discussion in the HTML 4.01 recommendation is here: http://www.w3.org/TR/html4/struct/objects.html#include-maps and here: http://www.w3.org/TR/html4/interact/forms.html#h-17.4.1

Robert Burns

Comment 8 2007-08-21 04:26:44 PDT

Created attachment 16050 [details] This attachment replaces the previous one Shows how image map behavior is inconsistent across the three elements that support client-side image maps