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

Calendar: Date Grid Keyboard Support is not working #15276

Closed
ramyanuthal opened this issue Apr 15, 2024 · 3 comments
Closed

Calendar: Date Grid Keyboard Support is not working #15276

ramyanuthal opened this issue Apr 15, 2024 · 3 comments
Labels
Resolution: Needs More Information More information about the issue is needed to find a correct solution Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response

Comments

@ramyanuthal
Copy link

Describe the bug

When setting 'Time' for input field, holding down the up/down arrows should continue to scroll the numbers. Currently, this feature is not working. The arrows must be clicked each time the user wants the number to change.

Environment

My Environment details:
Angular: 16.2.9
node: 16.14.0
Primeng: 16.9.1
@ngrx/store": "^16.3.0"

Reproducer

No response

Angular version

16.2.9

PrimeNG version

16.9.1

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

16.14.0

Browser(s)

Microsoft Edge

Steps to reproduce the behavior

When setting 'Time' for input field, the up/down/side arrows should continue to scroll the numbers.

Expected behavior

Grid Keyboard Support should work with up/down/side arrows should continue to scroll the numbers.

@ramyanuthal ramyanuthal added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Apr 15, 2024
@cetincakiroglu
Copy link
Contributor

Hi,

Could you please create a stackblitz example so we can identify the issue?

@cetincakiroglu cetincakiroglu added Resolution: Needs More Information More information about the issue is needed to find a correct solution and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Apr 19, 2024
Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Aug 18, 2024
Copy link

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Needs More Information More information about the issue is needed to find a correct solution Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response
Projects
None yet
Development

No branches or pull requests

2 participants