Sebastian "Sebbie" Silbermann

> A case where I have a button text that is different than the accessible name And why can't you query by the accessible name? Why is it so important...

> // works, but fails unhelpfully if we somehow remove or change the accessible name. What do you mean "unhelpfully"? The error message should include the accessible names of each...

> Querying by accessible name, then asserting text is backwards from this mentality. Yeah this is where we disagree. The idea of this library is that we first consider a11y...

> By default, normalization consists of trimming whitespace from the start and end of text, and collapsing multiple adjacent whitespace characters into a single space. -- https://testing-library.com/docs/queries/about/#normalization The documentation matches...

Thanks for the feedback > I would expect it to wait for 5 seconds (unless I'm totally wrong 😅), It should wait for 5seconds in the **fake clock**. It used...

> This commit on the v11 branch works fine with the old behavior (with jest v26). I'm not sure how to test the same behavior with the new timer changes...

It seems to me `msw` is using a different clock. I would expect that if I advance the clock by 200ms and flush the microtask queue any response with a...

Let's keep this open since `msw` is quite popular and I'd like to ensure compatiblity short-term. I just don't know where to start so some response from their maintainers would...

> Maybe it needs to check if fake timers are enabled and in those cases run jest.advancedTimerBy(response.delay) ? That would already be handled by us. The only important part is...

> This was added a while ago so that fake timers in Jest don't interfere with the request handling. They shouldn't do that. The point of fake timers is that...