Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tabs Component: Discrepancy between WC and Angular #14816

Closed
SisIvanova opened this issue Sep 24, 2024 · 0 comments · Fixed by #14886
Closed

Tabs Component: Discrepancy between WC and Angular #14816

SisIvanova opened this issue Sep 24, 2024 · 0 comments · Fixed by #14886
Assignees
Labels
📈 enhancement keyboard-navigation tabs ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.

Comments

@SisIvanova
Copy link
Collaborator

Description

The keyboard navigation of the Ignite UI for Angular Tab component differs from the one in WC.
Following this feature request, the scroll buttons have been excluded from the keyboard navigation but this enhancement hasn't been implemented in Angular.

Steps to reproduce

  1. Open a Tabs with scroll sample and start navigating using the Tab key.
  2. Make the same test but in Web Components

Expected result

Both components should behave the same.

Attachments

Screen.Recording.2024-09-24.at.2.mp4
@MonikaKirkova MonikaKirkova added 🛠️ status: in-development Issues and PRs with active development on them 📈 enhancement and removed 🆕 status: new 🐛 bug Any issue that describes a bug labels Oct 4, 2024
@MonikaKirkova MonikaKirkova added ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged. and removed 🛠️ status: in-development Issues and PRs with active development on them labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📈 enhancement keyboard-navigation tabs ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants