Behavior of waitForElementToBeRemoved when first call throws

• @testing-library/dom version: 8.11.2

Problem description:

There is currently no exception catching for the initial call inside waitForElementToBeRemoved. When that call of callback throws, instead of getting the error Error('The element(s) given to waitForElementToBeRemoved are already removed...') we will get the error thrown from the callback, even when it is a TestingLibraryElementError. This contradicts the documented behavior:

waitForElementToBeRemoved(() => getByText(/not here/i)).catch(err =>
  console.log(err),
)
// Error: The element(s) given to waitForElementToBeRemoved are already removed. waitForElementToBeRemoved requires that the element(s) exist(s) before waiting for removal.

Suggested solution:

See #1094.

Start with src/wait-for-element-to-be-removed.js, especially the initial callback invocation linked in the issue, and compare it with the documented behavior. Review the related discussion in #1094; done means an initial callback failure produces the documented already-removed error when appropriate, rather than exposing the callback's Testing Library error.