1. Feedback
  2. Angular
  3. 57942

Welcome to the Angular feedback portal. We’re happy you’re here! If you have feedback on how to improve the Angular, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

In a cell template with multiple interactive fields, neither of those fields receives focus with keyboard nav

If you have a cell template that has multiple interactive fields, such as an input and a select, or 2 inputs, neither of those fields receives focus when using the tab key on the keyboard to navigate to the cell. As far as I can tell, there is no way to interact with those elements at all, using keyboard navigation. If there is only a single interactive field, that field is given focus as soon as the user tabs to the cell, so it is not a problem then. But when there are multiple interactive fields, the focus stays on the cell itself. Here is a simple cell template that can be used to reproduce the problem:

        <e-column headerText="Returned" width="100">
        <ng-template #template let-data>
        <input [ngModel]="data.amountReturned">
                <br>
                <input [ngModel]="data.amountReturned * data.foodItem.formulaYield">
            </ng-template>
        </e-column>

Something that's even more bizarre is that if I first click on a cell within the grid, and then tab to a cell with multiple interactive fields, then focus moves back to the cell that I had previously clicked on. Even if I had tabbed through multiple cells before getting to the one with multiple interactive fields, it always moves focus back to the last cell I had clicked on. The blue outline will be around the cell with the interactive fields, but the document.activeElement property shows that the focus is actually on the cell that was previously clicked on. Maybe this is a separate bug, but it seems closely related, so I'm including its details here.

I have a workaround for this bug by handling the internal "cellfocused" event to focus the first interactive element in the cell, but the bug itself still remains.