- From: Majid Valipour <notifications@github.com>
- Date: Thu, 22 Jun 2017 13:49:23 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 22 June 2017 20:49:55 UTC
@annevk thanks for bearing with me on this. So I just added a new commit which I think should address your feedback. Here are the changes I made: Normative definition of timeStamp attribute now defines that it should be initialized to equivalent of performance.now() on creation. I also added warning about 5 microsends minimum resolution from hrtime spec and referenced that spec. I also added details on how this attribute should be initialized in each algorithm where we create or construct an Event. * On event creation, if available the occurrence time should be used to initialize the property. * On event construction or when `Document.createEvent` is used, the time that the method is invoked should be used. ** ** I actually feel that this may not be necessary since the attribute definition specifies the same but I followed the example of how `isTrusted` is spec'd. :confused: -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/420#issuecomment-310498448
Received on Thursday, 22 June 2017 20:49:55 UTC