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

Slider: Change range slider by keys does not trigger the onSlideEnd event #15107

Closed
avytak opened this issue Mar 20, 2024 · 0 comments · Fixed by #15738
Closed

Slider: Change range slider by keys does not trigger the onSlideEnd event #15107

avytak opened this issue Mar 20, 2024 · 0 comments · Fixed by #15738
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@avytak
Copy link

avytak commented Mar 20, 2024

Describe the bug

I'm using the range slider in my project with the onSlideEnd event. Currently, I'm working on improving the accessibility and see that when I change it using the keys - the onSlideEnd is not triggered, only onChange works.

Environment

Google Chrome

Reproducer

No response

Angular version

16.2.8

PrimeNG version

"^16.5.1" and for the latest version of PrimeNG

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.19.1

Browser(s)

122.0.6261.129 (Official Build) (64-bit)

Steps to reproduce the behavior

  1. Add p-slider with range attribute set to true
  2. Add onSlideEnd event with console.log function inside your component
  3. Try to slide using the keys after that press Tab.
  4. See that onSlideEnd wasn't triggered

Expected behavior

The event should be triggered after the Tab press

@avytak avytak added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Mar 20, 2024
@mehmetcetin01140 mehmetcetin01140 added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels May 20, 2024
@mehmetcetin01140 mehmetcetin01140 added this to the 17.17.1 milestone May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
2 participants