🐛 do not calculate resource duration if page was in frozen state during resource duration #3349
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
Fixes Bug with resource duration where incorrect due to page being in a frozen state sometime during the request.
The intention was to set duration to
undefined
when the page was in a frozen state during the request duration (computeRequestDuration
), however this was overridden bycomputeResourceEntryMetrics
.The unit tests where not catching the issue because no matching PerformanceResourceTiming was mocked.
Changes
computeResourceEntryMetrics
aware of frozen states and prevent calculating any durations when needed.Testing
I have gone over the contributing documentation.