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.

Sign up for GitHub

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

Jump to bottom

IgxSingleCombo: strange tab behavior when 2 single combos are next to each other #14791

Open
Timmeeeey opened this issue Sep 18, 2024 · 4 comments · May be fixed by #15279
Open

IgxSingleCombo: strange tab behavior when 2 single combos are next to each other #14791

Timmeeeey opened this issue Sep 18, 2024 · 4 comments · May be fixed by #15279
Assignees
@Lipata @Hristo313
Labels
🐛 bug Any issue that describes a bug combo ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.

Comments

@Timmeeeey
Copy link

Description

If you have 2 single combos next to each other that have a selected value and then click on the first one and press tab, then instead of just closing the dropdown the focus jumps to the next single combo. Each following tab doesn't do anything. The focus stays on the second combo.

  • igniteui-angular version: 18.1.11

Steps to reproduce

Normal behavior:
Pressing tab only closes the dropdown

2024-09-18_15h21_34

Wrong behavior:
Pressing tab focuses second dropdown. When pressing tab again, nothing happens.

2024-09-18_15h22_15

Attachments

https://stackblitz.com/edit/wpppeb
@Timmeeeey Timmeeeey added 🐛 bug Any issue that describes a bug 🆕 status: new labels Sep 18, 2024
@github-actions GitHub Actions
Copy link

There has been no recent activity and this issue has been marked inactive.

@github-actions github-actions bot added the status: inactive Used to stale issues and pull requests label Nov 18, 2024
@Lipata Lipata removed the status: inactive Used to stale issues and pull requests label Nov 18, 2024
@Hristo313 Hristo313 added 🛠️ status: in-development Issues and PRs with active development on them 💥 status: in-test PRs currently being tested 👀 status: in-review Issue is currently being reviewed and removed 🆕 status: new 🛠️ status: in-development Issues and PRs with active development on them 💥 status: in-test PRs currently being tested labels Dec 9, 2024
@Hristo313
Copy link

@Timmeeeey What is described as "wrong behavior" is actually the expected behavior according to this comment: #14085 (comment). The normal behavior should ensure that pressing the Tab key moves focus to the next dropdown.

@Timmeeeey
Copy link
Author

@Hristo313 It's ok that the focus moves to the next dropdown.
The problem is that when pressing tab again, nothing happens. The focus is trapped in the second dropdown.

@Hristo313
Copy link

Hristo313 commented Dec 12, 2024 •
edited
Loading

@Timmeeeey Yes and if the dropdown is opened, pressing Tab should not only close it but also focus on the next dropdown, regardless of if the next focusable input has value or not.

@Hristo313 Hristo313 added 🛠️ status: in-development Issues and PRs with active development on them and removed 👀 status: in-review Issue is currently being reviewed labels Jan 16, 2025
@Hristo313 Hristo313 mentioned this issue Jan 16, 2025
Closed
14 tasks
@Hristo313 Hristo313 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 Jan 16, 2025
@Hristo313 Hristo313 linked a pull request Jan 22, 2025 that will close this issue
Open
14 tasks
This was referenced Jan 30, 2025
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Lipata Lipata

@Hristo313 Hristo313

Labels
🐛 bug Any issue that describes a bug combo ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.
Projects
None yet
Milestone
No milestone
4 participants
@ChronosSF @Lipata @Timmeeeey @Hristo313