@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.
@testing-library/domversion: 8.11.2Problem description:
There is currently no exception catching for the initial call inside
waitForElementToBeRemoved. When that call ofcallbackthrows, instead of getting the errorError('The element(s) given to waitForElementToBeRemoved are already removed...')we will get the error thrown from the callback, even when it is aTestingLibraryElementError. This contradicts the documented behavior:Suggested solution:
See #1094.