Table : update edit mode tab to navigate

[prashanthr6383]

Description

References

Fixes #2437

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[netlify]

✅ Deploy Preview for moduswebcomponents ready!

Name	Link
🔨 Latest commit	5b55616
🔍 Latest deploy log	https://app.netlify.com/sites/moduswebcomponents/deploys/674f0ed97e719e00087890f8
😎 Deploy Preview	https://deploy-preview-2870--moduswebcomponents.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 42 (🔴 down 5 from production) Accessibility: 75 (no change from production) Best Practices: 92 (no change from production) SEO: 100 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[prashanth-offcl]

@prashanthr6383 Regarding the issue Dateinput field edit mode is not updated when tabbing through cells you can assign handleBlur to onDateInputBlur prop of modus-data-input component.

Apart from the issue you brought up, I see the autocomplete dropdown and date picker dropdown is not appearing as before when I press tab. Can you check that?

[vetrivel1]

File: stencil-workspace/src/components/modus-table/parts/cell/modus-table-cell-main/modus-table-cell-main.tsx (line 174-186)
The tab navigation code in this block could be refactored into a separate method to reduce duplication with the existing NavigateTableCells utility. The tab and shift+tab handling logic in this component is complex and should be better documented.

File: stencil-workspace/src/components/modus-table/utilities/table-cell-navigation.utility.tsx (line 33-45)
The navigation utility now handles 'shift+tab' and 'tab' cases, but uses different logic than arrow key navigation. Consider unifying the approach for better maintainability. Also, the naming and type safety could be improved - prevCell and nextCell are both of type HTMLElement, but later in the code they're accessed as if they have specific Stencil component methods.

File: stencil-workspace/src/components/modus-table/parts/cell/modus-table-cell-main/modus-table-cell-main.tsx (line 187)
The call to componentOnReady().then() assumes the component will always be ready and doesn't handle potential errors or rejection. Consider adding error handling for cases where the component might not be ready.

File: stencil-workspace/src/components/modus-table/utilities/table-cell-navigation.utility.tsx (line 17-18)
The new optional parameters (isCellEditable and onNavigateComplete) are only used for tab navigation. Consider separating these concerns or add documentation explaining why these parameters are tied specifically to tab navigation.

Diff reference