169548 2017-03-13 03:52:48 -0700 Spec change: <img ismap> coordinates should be from image edge, not border edge 2017-05-22 02:27:33 -0700 1 1 1 Unclassified WebKit DOM Safari Technology Preview Unspecified Unspecified NEW FromImplementor, WebExposed P2 Normal --- 1 zcorpan webkit-unassigned cdumez sabouhallawa simon.fraser oldest_to_newest 1287130 0 zcorpan 2017-03-13 03:52:48 -0700 Demo: http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=3800 Expect click on border in the top-left corner to get coordinates 0,0. WebKit measures from the border edge instead. whatwg/html issue: https://github.com/whatwg/html/issues/438 whatwg/html change: https://github.com/whatwg/html/pull/529 web-platform-test: https://github.com/w3c/web-platform-tests/pull/5118 The test passes in Chromium and Gecko; fail in WebKit and Edge. Comment from Travis (Edge) https://github.com/w3c/html/issues/492#issuecomment-285819148 > Definitely makes sense just to align with Chrome/Firefox on this... 1289685 1 cdumez 2017-03-20 19:45:53 -0700 Likely the code in appendServerMapMousePosition(). Looks like link has some extra logic there: // The origin (0,0) is at the upper left of the content area, inside the // padding and border. mapPoint -= toLayoutBox(layoutObject)->contentBoxOffset(); 1289686 2 cdumez 2017-03-20 19:46:15 -0700 (In reply to comment #1) > Likely the code in appendServerMapMousePosition(). Looks like link has some > extra logic there: > // The origin (0,0) is at the upper left of the content area, inside the > // padding and border. > mapPoint -= toLayoutBox(layoutObject)->contentBoxOffset(); s/link/Blink 1311263 3 zcorpan 2017-05-22 02:27:33 -0700 https://github.com/w3c/web-platform-tests/pull/5118 has now landed.