Has there been any progress on the date being identical on all saved entries, down to the same second?
Don't the new webext APIs have a time API? Is it no longer possible for a program to read the computer's clock?
Having the correct time hasn't been a huge issue for me - yet, but I can see how it could become one.
Better days ahead!
* UPDATE:
I just noticed that the 2 comments I typed on this site showed different* clock times than all previous messages.
All the message still show today's date - even ones from weeks ago. But until tonight - on this site, ALL messages showed exact same date & clock time. 3/25/2018 3:05:49 PM.
Don't know if you looking at how Github interacts w/ the time recorded in TACL will help, but it seems to be different than all other sites.
I found that I was using Date object as an attribute of saved cache, maybe it is the criminal of invalid date.
I will update it in the version 4.2.0. and let see whether this problem will be solved...
Has there been any progress on the date being identical on all saved entries, down to the same second? Don't the new webext APIs have a time API? Is it no longer possible for a program to read the computer's clock? Having the correct time hasn't been a huge issue for me - yet, but I can see how it could become one. Better days ahead! * UPDATE: I just noticed that the 2 comments I typed on this site showed different* clock times than all previous messages. All the message still show today's date - even ones from weeks ago. But until tonight - on this site, ALL messages showed exact same date & clock time. 3/25/2018 3:05:49 PM.
Don't know if you looking at how Github interacts w/ the time recorded in TACL will help, but it seems to be different than all other sites.