Kai Dederichs

@j-krl how'd you do that exactly? From what I found you get no access to the lists scrollHeight and scrollTop since the only thing the ref exposes is the ref.scrollToBottom...

Kind of works yeah, though since it's an inner component you can't just slap an ID on it.... you actually have to do ```js document?.getElementsByClassName( 'scrollbar-container', ) ``` and then...

I'm facing the same issue. I think what's happening is that the it's only fetching new elements on hard top position, not a margin. So when you reach the end,...

Getting the same error locally (Mac book) and worse on a linux server (Ubuntu 20) while trying to deploy the app via script. No Sentry in our case though so...

Hmmm that's annoying. I'd assume Apple does some stuff in regards to their hardware then? Cause those auto connect when near, so I assumed it might be possible for other...

Seems to be a bit of a false positive somewhere tbh. When you straight up delete the deprecated class locally and run tests it'll work fine and without deprecation

I tried the same I did with the example above using mockResponses to see if that changes the result. It does not. Another thing to note is that ```fetch.mock.calls.length``` is...

The test looks something like this: ``` fetch.once('', { headers: { 'Content-Type': 'application/json' }, status: 503, }); fetch.once(addressDeleteSuccess, { headers: { 'Content-Type': 'application/json' }, status: 200, }); await sagaTester.dispatch(setAccessToken('123')); await...

That fixed half of my problem I'd say. Now the responses will correctly cycle through but it still doesn't increase the ```fetch.mock.calls.length``` constantly being 1. Unless I misunderstood what this...

Sorry, took me a bit but here is a repo with one simple test case showing that behavior: https://github.com/KDederichs/fetch_mock_test