This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14464 - 4.8.14.2 requires firing two events although no browser does that
Summary: 4.8.14.2 requires firing two events although no browser does that
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-14 15:09 UTC by Olli Pettay
Modified: 2011-10-24 23:09 UTC (History)
4 users (show)

See Also:


Attachments

Description Olli Pettay 2011-10-14 15:09:13 UTC
"Pointing device interaction with an image associated with a set of layered shapes per the above algorithm must result in the relevant user interaction events being first fired to the top-most shape covering the point that the pointing device indicated (if any), and then fired again (with a new Event object) to the image element itself."

Based on testing if one clicks over a shape, only the area element gets
event, image element doesn't.
Tested IE9, FF10, ChromeXX, Opera 11.50

Testcase:
http://mozilla.pettay.fi/moztests/imagemap.html
Comment 1 Ian 'Hixie' Hickson 2011-10-14 18:24:35 UTC
Weird, I could have sworn browsers did this. I wonder what the difference was between my tests are your test. Will have to investigate further.
Comment 2 Ian 'Hixie' Hickson 2011-10-24 23:07:09 UTC
I really was sure I had tested this. But apparently not. I wonder where my original text came from (it seems to have appeared in r581 in 2007 and I can't find a paper trail for it.)



EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 3 contributor 2011-10-24 23:09:09 UTC
Checked in as WHATWG revision r6736.
Check-in comment: Compatibility. http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1227
http://html5.org/tools/web-apps-tracker?from=6735&to=6736