Within the tab group , always the selected tab must receive the first tab focus.
Can you handle that on the application side
No
Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)
All
If this is a bug, please provide steps for reproducing it; the exact components you are using;
Use Icon tab bar and select a tab that is not the first one.
Now, start navigating UI from screen start through keyboard.
Even though the ‘Item 1’ tab is in the selected state but when user use tab key to navigate all the UI elements always the ‘Item 0’ tab receives the first tab focus in the tab group.
Please provide relevant source code (if applicable).
Please provide stackblitz example(s).
You can try ngx examples, issue is reproducible there.
In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.
Yes, issue is raised by an accessibility expert.
Did you check the documentation and the API?
Yes
Did you search for similar issues?
Is there anything else we should know?
IMPORTANT: Please refrain from providing links or screenshots of SAP's internal information, as this project is open-source, and its contents are accessible to anyone.
Is this a bug, enhancement, or feature request?
Bug
Describe your proposal.
Within the tab group , always the selected tab must receive the first tab focus.
Can you handle that on the application side
No
Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)
All
If this is a bug, please provide steps for reproducing it; the exact components you are using;
Component Used: Icon Tab Bar
Steps to reproduce:
Please provide relevant source code (if applicable).
Please provide stackblitz example(s).
You can try ngx examples, issue is reproducible there.
In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.
Yes, issue is raised by an accessibility expert.
Did you check the documentation and the API?
Yes
Did you search for similar issues?
Is there anything else we should know?
IMPORTANT: Please refrain from providing links or screenshots of SAP's internal information, as this project is open-source, and its contents are accessible to anyone.