Bug 48923
| Summary: | [Web Timing] Enable by default | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Tony Gentilcore <tonyg> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | andyhume, ddkilzer, joepeck, sam, simon.fraser, simonjam |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 42434, 48922 | ||
| Bug Blocks: | 30685 | ||
Tony Gentilcore
After the vendor prefix is removed, we should enable the interface by default.
Assuming that the detailed timings are not passed up by the network stack for each port (bug 42432, bug 42433, bug 42434, bug 42435), we should repurpose the --enable-web-timing flag to guard just the network stack related timings (domainLookupStart, domainLookupEnd, connectStart, connectEnd, requestStart, responseStart, responseEnd) instead of the whole interface.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Tony Gentilcore
Sam, Simon, the http://test.w3.org/webperf/specs/NavigationTiming/ has reached the last call phase and the webkit implementation is in complete compliance (as far as we are best aware). It has also been enabled for the chromium port since the Chrome 6 stable release and the Qt port for a shorter time.
Do you think enabling by default in WebKit (with network stack times guarded) is the way to go or are there reasons to hold off?
Joseph Pecoraro
It looks like all ports enable WEB_TIMING by default right now. Lets close this out.