-
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
[Feature] Flow Direction demos for the sample app #4515
Labels
feature request 📬
A request for new changes to improve functionality
In-PR 🚀
labs 🧪
Marks an issue/PR involved with Toolkit Labs
Comments
Avid29
added
the
feature request 📬
A request for new changes to improve functionality
label
Mar 21, 2022
Hello, 'Avid29! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future! |
4 tasks
ghost
added
the
In-PR 🚀
label
Mar 21, 2022
ghost
removed
the
In-PR 🚀
label
Mar 23, 2022
4 tasks
ghost
added
the
In-PR 🚀
label
Mar 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature request 📬
A request for new changes to improve functionality
In-PR 🚀
labs 🧪
Marks an issue/PR involved with Toolkit Labs
Describe the problem
Proper right to left behavior isn't always clear. Toolkit maintainers likely don't test their controls in RTL flowing languages and developers writing with RTL flowing languages in mind don't always know the proper behavior.
Adding a Flow Direction option next to theme in the SampleController would at least allow Toolkit maintainers to easily test the behaviors of the controls more easily, and developers using the toolkit to more easily check the behavior of these controls in that context.
Describe the solution
I have added a Flow Direction ComboBox next to the theme ComboBox that changes the flow direction in the demo area.
Alternatives
Enter
FlowDirection="RightToLeft"
in the root element of the XAML pageAdditional info
No response
Help us help you
No response
The text was updated successfully, but these errors were encountered: