| Summary: | [WebTiming] responseEnd should always be >= responseStart | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Tony Gentilcore <tonyg> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | Normal | CC: | burg, pfeldman, simonjam |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 58354 | ||
| Bug Blocks: | 30685 | ||
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. |
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.