Fix issue 328 by using requestAnimationFrame

[chbonser]

Addresses #328. Wrap the ResizeObserver callback in a requestAnimationFrame to fix ResizeObserver loop limit exceeded exceptions.

Note: This may not be a perfect solution. See dialog on this response in stack overflow https://stackoverflow.com/a/58701523/985641.

[elwayman02]

I'd like to avoid this approach for the reasons outlined in that SO post here: https://stackoverflow.com/questions/49384120/resizeobserver-loop-limit-exceeded/58701523#comment118281231_58701523

Essentially, we shouldn't be working around an error message that doesn't actually impact our code at all by introducing a behavioral change that will create inconsistencies in the layout changes triggered by ResizeObserver. The suggestion in #328 is to catch the error and silence it without changing the behavior, so we should be doing that or nothing at all, IMO.

[chbonser]

Understood. I struggled to find the right way to catch and suppress a global exception in qunit. Any tips?

[elwayman02]

I'm not sure either. You could probably look into using one of window.onerror, QUnit.onError, or Ember.onError, unless there's a way to catch the error from the ResizeObserver itself. I'm not sure it's appropriate for this package to mess with QUnit directly, since consumers might be using Mocha or another test framework instead.

[elwayman02]

Perhaps this would help? https://api.qunitjs.com/extension/QUnit.onUncaughtException/

[elwayman02]

Fixed by #506