-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
NumericUpDown not focusable by pressing tab #3654
Labels
Comments
corvinsz
added
bug
evaluation required
Items is pending review or evaluation by the team
labels
Aug 21, 2024
corvinsz
added a commit
to corvinsz/MaterialDesignInXamlToolkit
that referenced
this issue
Aug 21, 2024
…ult NumericUpDown control
IsTabStop=false solves the annoying useless tabStop on the outer part of the control. However when you programmatically focus the NumericUpDown control, it is the outer control that gets the focus, not the textbox part which in my opinion should be the default. |
corvinsz
added a commit
to corvinsz/MaterialDesignInXamlToolkit
that referenced
this issue
Aug 22, 2024
…le moving focus with tab (and shift+tab) MaterialDesignInXAML#3654. Also removed the IsTapStop on the Template because that is not longer needed
@jamesport079 I agree with you. I opened a PR #3656 that should make the |
Keboo
added
up-for-grabs
and removed
evaluation required
Items is pending review or evaluation by the team
labels
Dec 2, 2024
Keboo
added a commit
to corvinsz/MaterialDesignInXamlToolkit
that referenced
this issue
Jan 3, 2025
…ult NumericUpDown control focus PART_TextBox of NumericUpDown control if it gets focus and enable moving focus with tab (and shift+tab) MaterialDesignInXAML#3654. Also removed the IsTapStop on the Template because that is not longer needed renamed variable (copy paste mistake) Applying code suggestions 31659b
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug explanation
When trying to focus the
NumericUpDown
control via tab (or shift+tab) theTextBox
is not focused, but rather the entire control itself:Version
5.1.0
The text was updated successfully, but these errors were encountered: