[Webkit-unassigned] [Bug 58143] PerformanceTiming returns inconsistent values when timing is null.

Mon Apr 11 10:33:59 PDT 2011

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

Vsevolod Vlasov <vsevik at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #88876|review-                     |review?, commit-queue?
               Flag|                            |

--- Comment #6 from Vsevolod Vlasov <vsevik at chromium.org>  2011-04-11 10:33:59 PST ---
(From update of attachment 88876)
View in context: https://bugs.webkit.org/attachment.cgi?id=88876&action=review

>> Source/WebCore/page/PerformanceTiming.cpp:264
>> +        return requestStart();
> 
> You probably should do the same for the secureConnection timers above and for the responseEnd below.

secureConnection: "If this attribute is available but HTTPS is not used, this attribute must return zero.", so zero is correct.
respondEnd is filled from documentLoadTiming, not resourceLoadTiming, so its value is correct as well.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.