🐛 do not calculate resource duration if page was in frozen state during resource duration

Author: thomas-lebeau

packages/rum-core/src/domain/resource/resourceCollection.ts

@@ -1,4 +1,3 @@
-import type { ClocksState, Duration } from '@datadog/browser-core'
 import {
   combine,
   generateUUID,
@@ -95,15 +94,13 @@ function processRequest(
 
   const correspondingTimingOverrides = matchingTiming ? computeResourceEntryMetrics(matchingTiming) : undefined
 
-  const duration = computeRequestDuration(pageStateHistory, startClocks, request.duration)
-
   const resourceEvent = combine(
     {
       date: startClocks.timeStamp,
       resource: {
         id: generateUUID(),
         type,
-        duration,
+        duration: toServerDuration(request.duration),
         method: request.method,
         status_code: request.status,
         protocol: matchingTiming && computeResourceEntryProtocol(matchingTiming),
@@ -117,7 +114,11 @@ function processRequest(
     },
     tracingInfo,
     correspondingTimingOverrides
-  )
+  ) as RawRumResourceEvent
+
+  if (pageStateHistory.wasInPageStateDuringPeriod(PageState.FROZEN, startClocks.relative, request.duration)) {
+    resourceEvent.resource.duration = undefined
+  }
 
   return {
     startTime: startClocks.relative,
@@ -216,12 +217,6 @@ function computeResourceEntryTracingInfo(entry: RumPerformanceResourceTiming, co
   }
 }
 
-function computeRequestDuration(pageStateHistory: PageStateHistory, startClocks: ClocksState, duration: Duration) {
-  return !pageStateHistory.wasInPageStateDuringPeriod(PageState.FROZEN, startClocks.relative, duration)
-    ? toServerDuration(duration)
-    : undefined
-}
-
 /**
  * The status is 0 for cross-origin resources without CORS headers, so the status is meaningless, and we shouldn't report it
  * https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/responseStatus#cross-origin_response_status_codes