The timeStamp attribute must return the value it was initialized to. When an event is created the attribute must be initialized to the number of milliseconds that has passed since 00:00:00 UTC on 1 January 1970.
One could trap both new Event and document.createEvent to set the timeStamp accordingly but how do you intercept events created and dispatched by the browser?
One could add an event listener (capture phase) to the document that listens on "every" event type and write the timeStamp as close to the dispatch time but that would be an ugly hack.
- Are there any better ways to emulate
Event.timeStamp?
- Are there any potential traps with intercepting
new Event/new CustomEventanddocument.createEvent.
- Are there other ways to create events programmaticly ?
- Are there any potential issues with adding event listeners to
documentand manually settingtimeStampas early as possible ?
Source: Tips4all, CCNA FINAL EXAM
I couldn't find any place to intercept the creation of events that were generated by the browser rather than by user code. Your "ugly hack" seems to work okay though:
ReplyDeleteaddEventListener("click", function (e) {
Object.defineProperty(e, "timeStamp", {
get: function () { return 4; }
});
}, true);
Obviously you'd have to call addEventListener a bunch of times with whatever event names you're interested in. Note that setting the timeStamp directly has no effect, but defineProperty works. I only tested Chrome and IE9; I'm sure interop would be a mess since we're using a getter method.