[Webkit-unassigned] [Bug 174862] Performance API: Implement performance.timeOrigin

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jun 8 18:40:16 PDT 2021


https://bugs.webkit.org/show_bug.cgi?id=174862

--- Comment #4 from Alex Christensen <achristensen at apple.com> ---
Comment on attachment 430926
  --> https://bugs.webkit.org/attachment.cgi?id=430926
patch

View in context: https://bugs.webkit.org/attachment.cgi?id=430926&action=review

>> Source/WebCore/page/Performance.h:78
>> +    DOMHighResTimeStamp timeOrigin() const;
> 
> Is this time origin varied across origins?
> Otherwise, it can create cross-origin tracking vector, right?

This time stamp is in milliseconds since 1970, so it doesn't identify the user that way.
The value is from the time the DocumentLoader started loading the Document (seen in DOMWindow::performance) or the time that the Worker was created (seen in WorkerGlobalScope::WorkerGlobalScope) which should not lead to a tracking vector.  This value is already indirectly exposed through Performance::now, which is the number of milliseconds since this time.
I'm hoping this is covered by tests.  Waiting on EWS.  If it isn't, I'll write some.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210609/05330805/attachment-0001.htm>


More information about the webkit-unassigned mailing list