craggy cape
Hey folks, not sure where to ask this question, but after upgrading Ember from 5.5 to 5.10, we started getting this error. I'm not sure what leads to it, I can't reproduce.
From Sentry's Replays, it looks like it's not really affecting the app, and users continue to work with the app as usual.
Any idea what's causing it? Was it fixed in some Ember version?
pure latch
Not sure if exactly the issue, but similar can happen if a user has a browser extension that tries to change the DOM. Web frameworks have a hard time recovering when DOM is manipulated without them knowing
craggy cape
Could be, but doesn't seem to be browser extensions this time. We also get errors from controlled environments: Electron and JxBrowser, where extensions don't run.
pure latch
What libraries do you have? I wonder if any of them messed with he vm
craggy cape
The most significant ones are: ember-headlessui (practically everywhere) and ember-table
the issues are raised on different pages, also the ones that don't use ember-table
so the only things that are everywhere are the ember-headlessui, ember-concurrency, ember-apollo-client
hmm, maybe it's safe to ignore after all 🤔 It looks like those errors "don't happen itself". They happen after some other error. Maybe the original error breaks the rendering somehow
pure latch
yea, without a reproduction it's hard to find out
does your tracker record everything about your users browser?
do these errors happen for multiple users?
craggy cape
seems to be happening across the board. Multiple users, multiple browsers, systems, etc.
pure latch
Chrome 70?!
craggy cape
Yeah. That's JxBrowser we have embedded in our old app. Our few-year migration will finish this year. Finally, we are closing this chapter 😉
Electron 34 uses Chromium 132, fortunately
pure latch
I don't know how long ago we supported chrome that old