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 8798 - It seems Opera and Firefox now have coordinate (0,0) at the content edge instead of the border edge (and allow negative coordinates if clicking on the border). Consider revising this requirement to match Opera and Firefox. (Haven't tested IE.) [sp]
Summary: It seems Opera and Firefox now have coordinate (0,0) at the content edge inst...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-22 11:22 UTC by contributor
Modified: 2010-10-04 13:58 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-01-22 11:22:47 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#concept-input-type-image-coordinate

Comment:
It seems Opera and Firefox now have coordinate (0,0) at the content edge
instead of the border edge (and allow negative coordinates if clicking on the
border). Consider revising this requirement to match Opera and Firefox.
(Haven't tested IE.)  [sp]

Posted from: 194.103.203.174
Comment 1 Simon Pieters 2010-01-22 11:28:38 UTC 
Also specify that the padding is part of the coordinate space.
Comment 2 Ian 'Hixie' Hickson 2010-02-13 11:33:10 UTC 
Do you have any test cases handy for this? If not I can make some.
Comment 3 Ian 'Hixie' Hickson 2010-02-18 07:02:59 UTC 
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 4 contributor 2010-02-18 07:06:18 UTC 
Checked in as WHATWG revision r4779.
Check-in comment: Let's go with the saner Firefox/Opera behaviour here, as it's closer to the (still insane) IE behaviour than the WebKit behaviour we previously had...
http://html5.org/tools/web-apps-tracker?from=4778&to=4779