You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
problem with languages that use ltr instead of rtl, DirectionAttribute('ltr');
When I touch the enumerated list or checkbox option, even when using ltr in languages like Hebrew, the checkboxes and enumerated lists do not change, they remain in the position as if using rtl
Expected results
checkbox and the list number go to the beginning of the line on the right side
Actual results
checkbox and list number are at the beginning of the line on the left side
Code sample
default quill
Screenshots or Video
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
In my exploring the code, I have found that lists are implemented by hard coding the checkbox (or list number) into the left edge of the display irrespective of ltr or rtl.
You can see this if you change the text alignment to center or right - the checkbox stays on the left edge with the text floating in the center - which looks weird!
Fixing that is not trivial.
More complex is the issue you raise of Hebrew with LTR but checkboxes on the right which would need some kind of language lookup.
I think the whole concept of lists and alignments needs review.
Anyone have any comments or solutions?
Is there an existing issue for this?
Flutter Quill version
9.4.2
Steps to reproduce
problem with languages that use ltr instead of rtl, DirectionAttribute('ltr');
When I touch the enumerated list or checkbox option, even when using ltr in languages like Hebrew, the checkboxes and enumerated lists do not change, they remain in the position as if using rtl
Expected results
checkbox and the list number go to the beginning of the line on the right side
Actual results
checkbox and list number are at the beginning of the line on the left side
Code sample
default quill
Screenshots or Video
No response
Logs
No response
The text was updated successfully, but these errors were encountered: