performance.timing leak in ESR31
In TBB/ESR31, although we set dom.enable_preformance
to false, I still see nonzero performance.timing properties: For example:
> performance.timing
< PerformanceTiming { navigationStart: 0, unloadEventStart: 0,
unloadEventEnd: 0, redirectStart: 1411030797789, redirectEnd: 1411030797789,
fetchStart: 1411030797789, domainLookupStart: 1411030797789,
domainLookupEnd: 1411030797789, connectStart: 1411030797789,
connectEnd: 1411030797789 }
I suppose this is a regression in Firefox.