🔊 [RUMF-1445] Check if the page was discarded before a resource

[amortemousque]

Motivation

To investigate resource with long duration, check if the page has been discarded by the browser.

Changes

Add the document.wasDiscarded in resources

Testing

• Local
• Staging
• Unit
• End to end

---

I have gone over the contributing documentation.

[codecov-commenter]

Codecov Report

Merging #1945 (2ddb840) into main (353193c) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1945      +/-   ##
==========================================
- Coverage   93.14%   93.12%   -0.02%     
==========================================
  Files         142      142              
  Lines        5396     5395       -1     
  Branches     1222     1222              
==========================================
- Hits         5026     5024       -2     
- Misses        370      371       +1     

Impacted Files	Coverage Δ
...s/rum-core/src/domain/contexts/pageStateHistory.ts	80.48% <ø> (+5.48%)	⬆️
...rumEventsCollection/resource/resourceCollection.ts	100.00% <100.00%> (ø)
...rum-core/src/domain/contexts/foregroundContexts.ts	90.76% <0.00%> (-6.16%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[BenoitZugmeyer]

💬 suggestion: ‏maybe String((document as any).wasDiscarded) so you can differentiate between true/false/undefined?

[amortemousque]

I don't see the point of getting undefined. true and false should be okay but maybe I'm missing something?

[BenoitZugmeyer]

Not all browsers are supporting this API, so when it doesn't, the page_was_discarded property would be missing, and it would be a bit less trivial to know whether this property is missing because an older SDK has been used, because the FF was not enabled or because the browser don't support it.

That's why I think it might help if you had an explicit undefined value here.