If the cell was not already focused, triggering a custom cell action takes 2 clicks in Safari and Firefox. First one focuses the cell, second one triggeres the action. Works as expected in Chrome

I want to work on a fix for this. @chandlerprall can I get assigned?
@kshitij86 from https://github.com/elastic/eui/blob/master/CONTRIBUTING.md:
We do not, as a policy, assign issues to community members. If you find an issue that is not assigned, assume that you are welcome to work on it and can submit a pull request. Feel free to leave a comment to mark intent and avoid conflict.
Please go for it!
@kertal does this issue occur only with specific cell actions, like the ones in the GIF or with others as well? I'd also appreciate if you could help me in reproducing this using example code, please?
It鈥榮 a general issue, except for Chrome
@kertal How can I add a custom cell action like that to an example? Do I have to set one of the EuiDataGridCellValueElementProps? Because focusing the cell and selecting the text is possible by double cliking on my version on Firefox, so it must be caused only by adding those.
@kshitij86 there's a good example in our docs, have a look:
https://eui.elastic.co/#/tabular-content/data-grid-styling-and-control#column-cell-actions
@kertal If you take a look at the examples, they are clickable with a single click. Sort of having trouble reproducing this on Linux Mint. Do you think it could be a MacOS specific issue with Firefox?
this is possible, will check if it's also a Windows problem (when I'm allowed to used the windows machine), dear @timroes could you do linux flavored double check in Firefox?
I checked on Linux Firefox 83.0, it does not seem to be an issue there. In the above linked docs page @kertal shared it's triggered by a single click.
While I was trying to record the gif it happened to me once that it seemed not to trigger, but I have the feeling I might just not have hit the button in that case :D

@timroes Yes as the icon doesn't appear unless you hover over the right side, even I thought I had reproduced the issue.
I've checked again, and in the meantime, this has been fixes, so I'm closing it