Sebastian "Sebbie" Silbermann

But shouldn't a RegExp allow for the same behavior? Adding another API for the same thing would be problematic.

> Using a RegExp is a solution for some cases, but not all. What cases could not be solved with a RegExp?

> This contradicts the documented behavior: The documentation is contradicting itself already. It only says that it'll throw on `null` or empty arrays. But it doesn't say that `() =>...

I lean towards leaving this as undefined behavior. Since the accessible name is affected by styling, ignoring it leaves you in an awkward spot. It makes sense in this specific...

Could you post the markup for your table so that we can identify how testing-library should work?

Thanks for the report! I don't know if cypress-testing-library is doing something different. But just from the code you posted, it shouldn't find the second button ever since that is...

> The second time it should only search in the aria-modal=true subtree and only find that button. I think what we should rather add a filter for `modal: true`. Right...

I don't think we should implement this without further research. Before we implemented some `aria-*` filters that only consider the actual element not parents. So we need to be sure...

I seem to remember putting some notes into https://github.com/eps1lon/dom-accessibility-api concerning placeholder. So I would suggest doing some digging there. Then we need to double check what `accname` would say and...

> I'd imagine that support has only grown since then. Or not. In any case, we need to verify that claim. It might also be that AT just do this...