User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:18.104.22.168) Gecko/20100401 Firefox/3.6.3 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:22.214.171.124) Gecko/20100401 Firefox/3.6.3 When a checkbox click event is generated from a click on a related label then, the checkbox Event has a timeStamp set to 0. Reproducible: Always Steps to Reproduce: 1.click on a label linked to a checkbox 2. 3. Actual Results: The checkbox's event.timeStamp is zero. Expected Results: The timeStamp should have a significant value.
Note, DOM Events specification allows event.timeStamp to be zero.
Actually in Webkit the behavior of .timeStamp depends on the browser. Chrome does something, Safari something else. But yes , I agree would be good to have some reasonable value for .timeStamp. I need to update a patch for that.
And IIRC in Opera .timeStamp is always o
I know. Because of all the quirks and bugs I had to work around in Opera I would not call this browser a "reference" implementation...
Created attachment 445301 [details] Test case #2 "change" and "input" events on input and select elements also has timeStamp set to zero.
The issue (zero returning value) is no longer reproducible on Firefox 49.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
Never too late to be good, thanks!
You need to log in before you can comment on or make changes to this bug.