Closed Bug 1163413 Opened 10 years ago Closed 10 years ago

event.offsetX has event.pageX value in setTimeout

Categories

(Core :: DOM: Events, defect)

Product:
Core
Component:
DOM: Events
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: pavel.trehubau, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150502004003 Steps to reproduce: http://jsbin.com/qanaqabigo/2/edit?js,console,output Click on box in output panel. Actual results: event.offsetX has event.pageX value if it's used in function inside of setTimeout call. Expected results: event.offsetX should has the same value as it has before setTimeout call.
Product: Firefox → Core
Component: Untriaged → DOM: Events
Firefox 40: pageX:35, offsetX:26 | pageX:35, offsetX:35 Firefox 39: pageX:51, offsetX:42 | pageX:51, offsetX:51 Firefox 38: pageX:48, offsetX:undefined | pageX:48, offsetX:undefined Firefox 37: pageX:18, offsetX:undefined | pageX:18, offsetX:undefined Chrome 42: pageX:51, offsetX:43 | pageX:51, offsetX:43
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → All
Version: 39 Branch → Trunk
This is according to spec. https://drafts.csswg.org/cssom-view/#dom-mouseevent-offsetx If you don't like it, please take it up in www-style.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.