You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the populatePageViewPerformanceEvent method of PageViewPerformanceManager there are a couple of issues that need addressing.
For Browsers that support the Navigation Timing perf event the calculation of the "networkConnect" time via
var network = DateTimeUtils.GetDuration(navigationTiming.startTime, navigationTiming.connectEnd);
is always zero as the GetDuration() only returns a value if BOTH start and end are not zero, null or undefined, however, the startTime (according to https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) is now always zero
The scoping of the variables total, network, request, response, dom are incorrect, while the code seems to be working (with the current version) we should fix the scoping of these variables so they are not "defined" in the if / else clause to avoid a future break by a version of TypeScript, Uglify or browser JS implementation.
The text was updated successfully, but these errors were encountered:
In the populatePageViewPerformanceEvent method of PageViewPerformanceManager there are a couple of issues that need addressing.
var network = DateTimeUtils.GetDuration(navigationTiming.startTime, navigationTiming.connectEnd);
is always zero as the GetDuration() only returns a value if BOTH start and end are not zero, null or undefined, however, the startTime (according to https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) is now always zero
The text was updated successfully, but these errors were encountered: