-
Notifications
You must be signed in to change notification settings - Fork 1.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
RadialGauge UIA improvements #3544
Conversation
Thanks chingucoding for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌 |
@chingucoding Seems like The Toolkit-CI keeps failing. Everything looks good on your end? |
Seems like there was an issue with the header of the new test file, thanks for the reminder @Kyaa-dost ! |
@chingucoding still failing... Wondering if there is a conflict between the base class and variable. Not sure 🤔 |
Yes, that build failure was because of the RadialGaugeAutomationPeer inheriting from RangeBase peer now which also implements the IRangeValueProvider interface. Added |
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.
@chingucoding Thanks for the PR. Looks great and ready to 🚀 🚀
Hello @Kyaa-dost! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
@msftbot merge this pull request once it is approved by @vgromfeld |
Hello @Kyaa-dost! Because you've given me some instructions on how to help merge this pull request, I'll be modifying my merge approach. Here's how I understand your requirements for merging this pull request:
If this doesn't seem right to you, you can tell me to cancel these instructions and use the auto-merge policy that has been configured for this repository. Try telling me "forget everything I just told you". |
Fixes
Fixes #3537 , Fixes #3539 , Fixes #3542 (this PR is all we can do, see microsoft/microsoft-ui-xaml#3469)
The issues with the sample were caused by microsoft/microsoft-ui-xaml#3467 , switching to RangeBaseAutomationPeer as base class for the RadialGauge peer fixes that.
Afaik, the only thing we can (and should do) for #3542 is raise the appropriate event on the AutomationPeer.
PR Type
What kind of change does this PR introduce?
Bugfix
What is the current behavior?
RadialGauge is not accessible
What is the new behavior?
RadialGauge is accessible
PR Checklist
Please check if your PR fulfills the following requirements:
Other information
I left out the RangeSelector from this PR as fixing that controls behavior needs more discussion on how to approach that.