Hi,
CommonUI has it’s own universal Click/Back bindings that you can set up, I think the best option here will be to bind A to the Click action so that it can route through the CommonUI router instead of relying on the native Slate navigation. There’s some info in section 3 of the CommonUI docs, can you try binding that button to the default click action and see if that solves things for you? I think it should be fine to have separate bindings for the hold and non-hold version of the same key, that binding should “click” the invisible cursor that we use in CommonUI to hover the focused button (which is slightly different than “pressing” it via a key, but the end result should be the same). Let me know if that doesn’t work from you and we can see if there’s a workaround to try.
Best,
Cody