Bug 133469

Summary: [SOUP] ResourceLoadTiming.responseStart is always 0
Product: WebKit Reporter: Carlos Garcia Campos <cgarcia>
Component: PlatformAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: berto, cdumez, commit-queue, danw, gustavo, mrobinson, svillar
Priority: P2 Keywords: Gtk
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch svillar: review+

Description Carlos Garcia Campos 2014-06-03 01:02:16 PDT 
We are not recording the responseStart in the soup backend. Tests don't detect that because they time reported to the js API is always relative to the navigation time (navigation start + responseStart), and test using local files check that requestStart <= responseStart (and they are equal) and test using HTTP only check responseStart is not 0 (it can never be 0 unless navigationStart is 0).
Comment 1 Carlos Garcia Campos 2014-06-03 01:04:22 PDT 
Created attachment 232417 [details]
Patch
Comment 2 Sergio Villar Senin 2014-06-03 02:05:51 PDT 
Comment on attachment 232417 [details]
Patch

Doesn't it allow us to pass any extra test?
Comment 3 Carlos Garcia Campos 2014-06-03 02:12:28 PDT 
(In reply to comment #2)
> (From update of attachment 232417 [details])
> Doesn't it allow us to pass any extra test?

"Tests don't detect that because they time reported to the js API is always relative to the navigation time (navigation start + responseStart), and test using local files check that requestStart <= responseStart (and they are equal) and test using HTTP only check responseStart is not 0 (it can never be 0 unless navigationStart is 0)."

:-)
Comment 4 Carlos Garcia Campos 2014-06-03 05:04:39 PDT 
Committed r169560: <http://trac.webkit.org/changeset/169560>