-
Notifications
You must be signed in to change notification settings - Fork 13.4k
fix(picker): keyboard entry works with options #28652
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
Conversation
const findItemFromCompleteValue = values.find(({ text }) => { | ||
const parsedText = text.replace(/^0+(?=[1-9])|0+(?=0$)/, ''); | ||
const findItemFromCompleteValue = options.find(({ textContent }) => { | ||
const parsedText = textContent!.replace(/^0+(?=[1-9])|0+(?=0$)/, ''); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keyboard entry is currently only used inside of Datetime where we guarantee textContent is set. If we end up exposing this feature publicly we should revisit this assumption.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we move this to a comment directly in the code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added in a00f563
const findItemFromCompleteValue = values.find(({ text }) => { | ||
const parsedText = text.replace(/^0+(?=[1-9])|0+(?=0$)/, ''); | ||
const findItemFromCompleteValue = options.find(({ textContent }) => { | ||
const parsedText = textContent!.replace(/^0+(?=[1-9])|0+(?=0$)/, ''); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we move this to a comment directly in the code?
@liamdebeasi any idea when this update will be released? im not seeing keyboard navigation working for standalone ion-picker in v7.8.1 |
@mlakmal This fix can be found in v8 beta! If you want to test it out, then it's recommended to read the upgrade guide to v8 beta on the Frameworks docs site. |
Thanks for the info. But we have a hard dependency with angular 15. Are thr any plans to fix this in v7 ? |
We don't plan to backport this feature to |
Issue number: N/A
What is the current behavior?
As noted in #28622, keyboard entry was not migrated to minimize the amount of code changes that needed to be reviewed at once. Keyboard entry would be updated in a separate PR.
What is the new behavior?
ion-picker-column-option
elements in a picker column instead of theitem
property on the column.Does this introduce a breaking change?
Other information