Use Google Chrome APIs

[eligrey]

Google Chrome provides a plethora of useful methods that boomerang should make use of in their chrome.loadTimes and chrome.csi APIs. chromium.Interval could also be useful for high-resolution timing.

[bluesmoon]

API described sort of over here:
http://ecmanaut.blogspot.com/2010/06/google-bom-feature-ms-since-pageload.html

[bluesmoon]

So I can't add this in until I can confirm exactly what these times measure, ie, what the start and end points are. I can't find any documentation relating to that, but any pointers would be appreciated.

[eligrey]

I just added chromium.Interval to the bug. It's a timer with a μs resolution (on non-Windows OSes) as opposed to the ms resolution of Date. I happen to have a timer script that utilizes it, which serves as a good example.

[bluesmoon]

But that still doesn't tell me what the start and end points are, ie, does it measure from page unload, beforeunload, first byte, dns lookup, tcp connect, http request, or something else and does it stop at onload, ondomcontentready, first byte, last byte or something else?

Without this information I can't reliably match it to anything else we're measuring.

[eligrey]

Since there's no documentation on chrome.csi and chrome.loadTimes, you can always just check the source itself.

[bluesmoon]

ok, this helps somewhat. It looks like chrome.csi().pageT is what we want only if chrome.loadTimes.requestTime is not null. I think I can start with that and then add more checks later as I understand it better.

[bluesmoon]

Lookup w.chrome.csi() for timing information if the user is on chrome and other methods fail.
Closed by adc918f