Bug Tracker

Ticket #2708 (closed enhancement: fixed)

Opened 7 years ago

Last modified 7 years ago

Cross Browser event object

Reported by: narcvs Owned by:
Priority: major Milestone: 1.2.4
Component: core Version: 1.2.3
Keywords: Event, Timestamp Cc:
Blocking: Blocked by:

Description

When attaching an event, e.g. keydown, to an element using bind or keydown, the event object that gets passed in at trigger time is not cross browser. Notably, the timeStamp object does not have a value in IE 5/6, and is 0 in Opera 9.27.

Is there a concensus on making the event object cross platform, or leaving it as is? The timeStamp feature is very convenient for certain purposes, and should be reliable.

A possible fix would be to give it value

e.timeStamp = e.timeStamp
Number(new Date())

before passing it on to the event handler.

Change History

comment:1 Changed 7 years ago by narcvs

That's supposed to be

e.timeStamps = e.timeStamp || Number(new Date())

Silly me.

comment:2 Changed 7 years ago by flesler

You wrote timeStamps the first time.

Anyway.. I think this is enough:

e.timeStamp = e.timeStamp || +new Date;

comment:3 Changed 7 years ago by joern

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in [5280].

Note: See TracTickets for help on using tickets.