Closed
Bug 562197
Opened 14 years ago
Closed 8 years ago
checkbox click event from a click on a related label has a timeStamp set to 0
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mbonnier, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) 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.
Reporter | ||
Comment 1•14 years ago
|
||
Comment 2•14 years ago
|
||
Note, DOM Events specification allows event.timeStamp to be zero.
Reporter | ||
Comment 3•14 years ago
|
||
Indeed, from specification: "Used to specify the time (in milliseconds relative to the epoch) at which the event was created. Due to the fact that some systems may not provide this information the value of timeStamp may be not available for all events. When not available, a value of 0 will be returned. Examples of epoch time are the time of the system start or 0:0:0 UTC 1st January 1970." But if the timeStamp is available when the user clicks on the checkbox I assume it is provided by "the system". Therefore if the event is indirectly triggered from the user clicking on the associated label it should be set in the checkbox's event. From the JavaScript application's perspective, it does not make sense to have it set to zero when a user clicked on the label instead of the checkbox. Also the timeStamp value does not follow the spec as it is not the "time (in milliseconds relative to the epoch)" but rather seems to be the time relative to the last browser restart. WebKit provide both the correct timeStamp for label-triggered event as well as the value from the epoch. It should be desirable to have both fixed and have consistent behavior across browsers. Thanks.
Comment 4•14 years ago
|
||
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.
Comment 5•14 years ago
|
||
And IIRC in Opera .timeStamp is always o
Reporter | ||
Comment 6•14 years ago
|
||
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...
Reporter | ||
Comment 7•14 years ago
|
||
"change" and "input" events on input and select elements also has timeStamp set to zero.
Comment 8•8 years ago
|
||
The issue (zero returning value) is no longer reproducible on Firefox 49.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 9•8 years ago
|
||
Never too late to be good, thanks!
Assignee | ||
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•