Open rhuanbarreto opened 4 years ago
This error has eaten our entire quota of event reporting in sentry.io (bug report service) after a couple of days of integration. Throwing this as an error is causing financial cost and missing opportunities to fix real bugs.
What are the next steps to move this forward?
As more devs are starting using ResizeObserver, it makes them spend a lot of time figuring out what is going on until they find this issue and realize that their code is working fine.
I left some thoughts here: https://github.com/w3c/csswg-drafts/issues/5488#issuecomment-812279513
This is overwhelming taking over the web dev. world and folks are mostly just ignoring it. Sometimes for legitimate reasons, sometimes not.
https://github.com/w3c/csswg-drafts/issues/6173 attempts to describe ways to give levers as well so that developers can at least silence this on their own if they know it's right.
Following up the discussion in https://github.com/WICG/ResizeObserver/issues/38, they say that the error is benign, so it shouldn't trigger an error but a warning.