Opened 9 years ago

Closed 8 years ago

#3681 closed task (wontfix)

Track and possibly comment on W3C Resource Timing Spec

Reported by: mikeperry Owned by: mikeperry
Priority: Medium Milestone: TorBrowserBundle 2.3.x-stable
Component: Firefox Patch Issues Version:
Severity: Keywords:
Cc: g.koppen@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We need to keep an eye on, which promises to provide both local and network timing information to JS.

These timers do seem amenable to spoofing (and hopefully also JS hooking). I don't see a lot of breakage being due to them being wrong, and they are not event driven so we don't have to delay delivery. I'm guessing if these timers were wrong, at worst webapps would just make poor load balancing and latency reduction decisions (which I assume is their intended use?)

Here is the discussion thread on the webkit list:

Child Tickets

Change History (3)

comment:1 Changed 9 years ago by mikeperry

Milestone: TorBrowserBundle 2.3.x-stable

comment:2 Changed 8 years ago by gk

Cc: g.koppen@… added

comment:3 Changed 8 years ago by mikeperry

Parent ID: #3059
Resolution: wontfix
Status: newclosed

We're just going to disable this stuff, more so for the DOM rendering stages than for the network stages. See #6204 for more details, though.

Note: See TracTickets for help on using tickets.