⚗️ [RUMF-1499] Don't send duration for resources crossing a page frozen state #2255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
The resource duration for XHR and fetch is computed by the SDK if the corresponding resource timing isn’t found. If during the resource a page frozen state happens, we will wrongfully compute the duration:
In these cases the browser SDK will now send resources without duration.
Changes
Check if the request crossed a frozen state in resourceCollection.ts
Testing
I have gone over the contributing documentation.