Mute "ResizeObserver loop limit exceeded" exception

[troelslenda]

Which issue does this PR close?

This PR closes #2031

What is the new behavior?

No ResizeObserver exceptions thrown in Azure App Insight when navigating to select pages

/drb/investment/securities
/drb/investment/overview
/drb/inbox

Other routes should be thoroughly tested.

Does this PR introduce a breaking change?

• Yes
• No

It's unclear if the changes has any sideeffects. It should be tested.

Are there any additional context?

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Reminders

• Make sure you have implemented tests following the guidelines in: "The good: Test".
• Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).

Review

• Do a self-review.
• Request that the changes are code-reviewed
• Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)

When the pull request has been approved it will be automatically merged to master via automerge.

[MadsBuchmann]

Nice!

I think we should check the message field of the exception as to not unintentionally mute other exceptions.

The standard error message is "ResizeObserver loop completed with undelivered notifications." according to the spec. According to this guy Chromium based browser might have another message set tho for some reason.

Which i believe is the one you might be seeing when testing from an Android based phone.

So we might have to check both.

So something like the below i guess 🤷

catch(e) {
   if message is either chrome message or standard message: 
      do nothing 
   else: 
      throw(e); 
} 

[MadsBuchmann]

Also if this turns out to give problems or not work - let's revert to the requestAnimationFrame solution. But i think this one might be the least intrusive solution for now.

[RasmusKjeldgaard]

Reverted to the requestAnimationFrame due to time constraints.
The new proposed solution did not catch the error, and we need to investigate the error object a bit more to find out how to filter it. Unfortunately the process is slow, as we have to build kirby, install it in a project, and run the emulator to get feedback, so we will have to investigate more at a later time.