-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Add highContrast to FakeAccessibilityFeatures test #48486
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
Add highContrast to FakeAccessibilityFeatures test #48486
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
|
Hi @miquelbeltran! Welcome 🎉 and thank you for the contribution! I've checked in on the engine change this depends on. :) |
Piinks
left a comment
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.
Thanks for splitting this out to land without breaking! :)
Piinks
left a comment
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.
I am inclined to approve. @LongCatIsLooong, you had mentioned this being similar to another feature in flutter/engine#15343. @miquelbeltran provided some feedback there on that, do you have any objections to this change moving forward?
|
We should land the change in the engine before landing this. We should separately land a change to the framework to make |
|
@dnfield is right. I forgot that the engine will complain when you add Here is the example of
Adding that will actually open the door to making changes like this easier in the future! :) |
|
Sorry for the delay, I have added now the noSuchMethod override. |
|
Could you pull changes from upstream again? That should fix the test failure. |
Reference ticket: #48418 Requires changes from the flutter/engine project. Instead of a hard-coded false, read the value from the window.accessibilityFeatures. Add highContrast to fake window test
Reverted highContrast value, will be included in a new Pull-Request Co-Authored-By: Kate Lovett <katelovett@google.com>
|
Done! |
Piinks
left a comment
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.
This LGTM! Thank you for your continued work on this! 🎉
|
Once this lands, we should be able to move on to the follow-up engine change you have staged in flutter/engine#15343 :) |
Description
Add the
highContrastproperty to theFakeAccessibilityFeaturesclass.The
highContrastis going to be added to the classAccessibilityFeaturesin the PR: flutter/engine#15343Design change document: https://docs.google.com/document/d/1kePVlqWvJu5Ph0RL6wgg67F3SATmsJ8QY5N0S1MvaGg/edit
Related Issues
Related to #48418
Depends on flutter/engine#15343
Tests
FakeAccessibilityFeatureswhich is used in the Window and MediaQueryData tests.Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.I don't know how to use Flutter Analyze with a custom Flutter Engine, so I can't make it pass.
Test pass when I use my custom Flutter Engine.
Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].