-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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 Request] Spacing should have "start" and "end" directions #4660
Labels
Milestone
Comments
MajesticPotatoe
changed the title
Spacing should have "start" and "end" directions
[Feature Request] Spacing should have "start" and "end" directions
Dec 7, 2018
MajesticPotatoe
added
the
framework
Issues and Feature Requests that have needs framework-wide.
label
Apr 10, 2019
Will this be implemented and shipped into v2.0? |
jacekkarczmarczyk
added a commit
that referenced
this issue
Jun 10, 2019
8 tasks
jacekkarczmarczyk
added a commit
that referenced
this issue
Jun 10, 2019
dsseng
added a commit
that referenced
this issue
Jun 11, 2019
jacekkarczmarczyk
added a commit
that referenced
this issue
Jun 19, 2019
jacekkarczmarczyk
added a commit
that referenced
this issue
Jun 19, 2019
* feat(styles): add rtl/ltr start/end spacing and alignment fixes #4660 * refactor(VDataTable): use *-start instead of *-left * docs: add start/end descriptions * docs: add justify description
fixed by #7448 |
This was referenced Jul 23, 2019
Closed
This was referenced Jul 23, 2019
This was referenced Aug 13, 2019
This was referenced Sep 20, 2019
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What problem does this feature solve?
Having start and end directions for spacing could help a lot with designs that support both RTL and LTR.
What is your proposed solution?
s
- applies the spacing for*-left
in LTR and*-right
in RTL.e
- applies the spacing for*-right
in RTL and*-left
in LTR.Would really appreciate it if you could add it!
The text was updated successfully, but these errors were encountered: