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
Text editing RTL #11375
Comments
Specifically:
|
Any updates on RTL support for widgets? I'm writing an app that displays in both arabic & english. It's surprising to see no upvotes to this issue. I'm fairly certain that this is a very important requirement. From what I've read elsewhere in the site, flutter team values issues as much as the need. So, plz leave an upvote, bystanders. Edit: I just saw that there's an entire project within flutter that's dedicated to internationalization :) Link: https://github.com/flutter/flutter/projects/17#card-3918549 |
rtl is basically done, this is one of the few remaining issues. |
@Hixie Do you know where you got the idea of 2 cursors at a bi-di boundary? Is this still the behavior that we want for Flutter? @LongCatIsLooong Suggested putting the cursor under the character that would be deleted with a backspace. Maybe that's unconventional, though. |
It's what Android did when I filed the bug. I don't know if they still do it. Our text fields should be identical to the platform text fields (at least by default, but in general I think these are complicated enough that we shouldn't further complicate them by adding our own twist on these behaviours, just implementing all the platforms' default behaviours is confusing enough as it is). |
To be clear, Flutter still has problems with RTL text editing, but those are tracked in other issues. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Text fields need to have a bidi cursor that shows what direction they are going in.
The text was updated successfully, but these errors were encountered: