I just tried reproducing this issue, both in a standard app and a multi-page app, but could not reproduce this behaviour. Would it be possible to share this workbook? Or from your end reproduce this issue using dummy data and send me the JSON?
Would you also be able to confirm which version you're on?
i tried from a fresh app and couldn't replicate. tried:
split pane
stack container with expand contents
table with Fill width
hidden columns
auto column width
went back and forth changing width manually, hiding, and then selecting auto width
so i loaded some dummy data and exported JSON of the app with the bug. if the query get_carrier_groups fails, there is default data loaded in the transformer section of it that will work to demonstrate the bug.
let me know if i can change anything for a better export!
I've been testing this - on my side, it looks like the event fires as long as I am clicking in the action button column, but if I click directly on a column with text, it works. Is that what you're seeing? The fact that the action column takes up so much space, and the fact that the row highlight part works, makes this pretty confusing for end users
I can put in some requests to address this. Would you want the click event to register in the white space around the action button? How about when the end user clicks the action button? Would you just want the white space around the action to be narrower?
Again, let me know if it sounds like you're seeing something different.
Hi @Tess I think so yeah, so it's technically the whitespace around the row action button?
hmm it's tough to choose. i could see value in both. right now it does neither. and really it's an edge case because i am cramming a table into the sidebar and need every pixel of width i can get. if the row click event fires because a touchscreen x-y is 1 pixel outside the row action button, it would be annoying.
probably having any of the whitespace be considered a row click event would be good.
I guess you could always add the event to the button too but that doesn't help with the whitespace. If the team picks this up they'll have to make it an optional setting in order to be backwards compatible, so it would be configurable. I'll let you know if I hear any updates internally
Actually, @trz-justin-dev does changing the event type to select row + enabling select the row on action help? Since this table only allows single row selection, I hope that will work for now!
that could work, though it might just be easier to remove the Delete Row row action button and move it outside the table so it deletes whatever row is currently selected.
I've been testing this - on my side, it looks like the event fires as long as I am clicking in the action button column, but if I click directly on a column with text, it works. Is that what you're seeing? The fact that the action column takes up so much space, and the fact that the row highlight part works, makes this pretty confusing for end users
I guess you could always add the event to the button too 
but that doesn't help with the whitespace. If the team picks this up they'll have to make it an optional setting in order to be backwards compatible, so it would be configurable. I'll let you know if I hear any updates internally
Since this table only allows single row selection, I hope that will work for now!