Closed
Bug 960459
Opened 10 years ago
Closed 10 years ago
event.timeStamp is in µSeconds by receiving an WebSocket onmessage-Event
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 238041
People
(Reporter: m.schmid, Unassigned)
Details
(Whiteboard: [bugday-20140120])
Attachments
(1 file)
|
877 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release) Build ID: 20131205075310 Steps to reproduce: I receive onmessage events and want to use the event.timeStamp Actual results: The event.timeStamp-Value is in microseconds (three additional zeros at the end every time) For example: 1389863531321000 Expected results: The event.timeStamp-Value should by in milliseconds like in IE and Chrome (tested) For example: 1389863531321
|
||
Updated•10 years ago
|
Component: Untriaged → DOM: Events
Product: Firefox → Core
Whiteboard: [bugday-20140120]
|
||
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•