Hi Balaji,
We are simply trying to use the
Column template feature of the Grid, which says:
"The column template has options to display custom element instead of a field value in the column."
I was trying to keep the defect report as simple as possible, but I have enhanced the
sample to provide more context.
We have an incident catalog where the vast majority of incident's (99.99%) are 'low' or 'medium' priority and require no further information. However, one in every ten thousand incidents are 'critical', and *when* an incident is critical the "Actions Taken" *must* be input.
The incident AssessmentComponent (mocked in the sample) is a 3rd party "custom element" and has a great deal of internal logic. It chooses what to display and whether it collects a single piece of information or multiple pieces.
So back to the original report...
I'm sure you would agree that when a user click on something that is displayed by a custom element, they do *not* expect the Grid to re-focus on something else.
Again, you can see this demonstrated by clicking on the 'Actions Taken' input and note that it momentarily get's focus (due to the click) and then the Grid immediately hijacks the focus and moves it to the 'level' dropdown.
This seems like a pretty clear defect to me, but just disabling this forced focus "feature" would be an okay workaround.
Thanks,
-Earl