Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
var input = document.createElement("input");
input.onclick = function (ev) {
console.log(ev.timeStamp === 0 ? "WHY IS IT ZERO" : "It's not broken");
};
input.click()
var ev = document.createEvent("Event");
console.log(ev.timeStamp === 0 ? "THIS IS MADNESS" : "At least this works");
In firefox the first timeStamp is 0 and in chrome the timestamp is a sensible number.
In both firefox and chrome the second timeStamp is a sensible number.
Bug #238041 – nsDOMEvent::AllocateEvent assigns a PR_Now() into a PRUint32