your focus-trap must have at least one container with at least one tabbable node focus-trap

[NicolasLaverde]

Hi fellas,
I have some weird bug, for some extrange reason we get this bug in just one client is implementing our service ( some Cookie consent modal )
This client is getting this bug error =>

But when I open their web Page I can see this error at all. This happens to us several times.
What should be? Chrome or firefox version? why this can works in many clients in the script we create but not in 100% of them?

What's the cause of this error?

[stefcameron]

@NicolasLaverde Many people run into this error, unfortunately. It happens when the containers you gave when you setup your focus trap do not have -- or no longer have -- any tabbable elements in them, which means that focus will inevitably escape your trap because focus must always go somewhere.

If your trap does not have (or no longer has) any tabbable (and therefore focusable) elements in it, and it was not configured with a backup element (see the fallbackFocus option -- which must still be in the trap, but does not necessarily have to be tabbable (i.e. it has tabindex="-1", making it focusable, but not tabbable), you will get this error.

This happens often when people have traps related to elements that appear and disappear dynamically. Typically, the error will fire either as the element is being shown (because the trap gets created before the trapped children have been inserted into the DOM), or as it's being hidden (because the trapped children are destroyed before the trap is either destroyed or disabled). I have yet to see it related to browser vendors or versions.

[NicolasLaverde]

Thanks so much ! yeah you just need to include focusTrapOptions object

[stefcameron]

Glad it helped. I decided to add a section in the README about it.