I pointed out in the support forum 2 issues I was having few days with the EO.Grid web control. The first one was quickly solved with a new build. Unfortunately the second one was not a behaviour still contemplated and there was no way to achieve the result I was expecting.
Here you can find the conversation I'm talking about
The feature I'd like to have on the Grid control, it's the possibility to declare some specific columns as "navigable=true/false" (or something like that) to describe a sequence of navigability while in keyboard navigation mode (the attribute would be =true by default). Well actually not a real sequence.. because the order would remain unchanged, but at least the possibility to totally exclude a column from the keyboard navigation so that readonly fields would not even be considered. This may be the easiest approach to achieve the result. But I would agree even with more complex strategies like clientside events to control the cursor landing on the cell and clientside actions to redirect the cursor elsewhere.
I don't expect this feature to be really implemented, but since I already talked about it in the support forum and there is a specific section for this kind of request, I thought it was fair enough to give it a try.
Thanks