-
Notifications
You must be signed in to change notification settings - Fork 9.3k
Fix failing UIA tests from #10886 #10924
Copy link
Copy link
Closed
Labels
Area-AccessibilityIssues related to accessibilityIssues related to accessibilityIssue-TaskIt's a feature request, but it doesn't really need a major design.It's a feature request, but it doesn't really need a major design.Product-TerminalThe new Windows Terminal.The new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.
Milestone
Metadata
Metadata
Assignees
Labels
Area-AccessibilityIssues related to accessibilityIssues related to accessibilityIssue-TaskIt's a feature request, but it doesn't really need a major design.It's a feature request, but it doesn't really need a major design.Product-TerminalThe new Windows Terminal.The new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.
Type
Fields
Give feedbackNo fields configured for issues without a type.
#10886 follow-up
There's some failing tests in the CSV that we're skipping right now. They shouldn't be failing, but the tests were verified to be correct when comparing our behavior to MS Word's.
We should update our UIA implementation to make these tests not fail.
IIRC I believe the failing tests are mainly: