ionic-team / ionic-team/ionic-framework
feat: ionKnobMoveStart/End expose info on which knob is moving
- Lingua principale
- TypeScript
- Stelle
- 52.7k
- Fork
- 13.3k
- Merge medio
- 1g 15h
- PR unite (30g)
- 51
Descrizione
### Prerequisites
- [X] I have read the [Contributing Guidelines](https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#creating-an-issue).
- [X] I agree to follow the [Code of Conduct](https://ionicframework.com/code-of-conduct).
- [X] I have searched for [existing issues](https://github.com/ionic-team/ionic-framework/issues) that already include this feature request, without success.
### Describe the Feature Request
You can have two knobs on an ion-range, and we have these two new events ionKnobMoveStart and ionKnobMoveEnd, but I can't figure out which knob got moved from the event. Please provide that info in the passed $event or somehow.
### Describe the Use Case
I have different behaviors for the two knobs in the range.
### Describe Preferred Solution
Probably in the range event detail, let us know which knob was moved.
### Describe Alternatives
I could do this with (touchstart) and (touchend), but those don't do the keyboard control, right?
### Related Code
_No response_
### Additional Information
_No response_
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start at the ion-range implementation and the definitions for ionKnobMoveStart and ionKnobMoveEnd. Trace the range event detail to determine how the moving knob can be identified, including keyboard interaction. Done means both events expose which knob moved while retaining the existing range behavior.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- typescript
- Ambito
- frontend
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 42/100