Bug 53305 - [WebTiming] responseEnd should always be >= responseStart
Summary: [WebTiming] responseEnd should always be >= responseStart
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 58354
Blocks: 30685
  Show dependency tree / graph
 
Reported: 2011-01-28 08:36 PST by Tony Gentilcore
Modified: 2014-12-15 23:38 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Gentilcore 2011-01-28 08:36:08 PST 
I've received at least one report of the following:
> responseEnd: 1296224561282
> responseStart: 1296224561283

It should be impossible for the start to be after the end. Unfortunately, I don't know how to repro this.
Comment 1 James Simonsen 2011-02-01 16:45:23 PST 
It could be that the clock skewed backwards at a bad time. We have no protection against that. We should bring this issue up with the WG.