Disabling container doesn't disable table within container

I'm trying to disable a container when certain conditions are hit, however the new table component doesn't appear to be disabled in any way despite being a child component of the table.

It's currently still possible to select rows, click toolbar functions and interact with table actions, which means that users may still be able to complete table actions that should be disabled by the parent container being disabled.

Thanks for flagging this, @Milo! Our team is looking into this bug :disappointed: I'll post here with any updates that I get