Skip to content
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

Introduce [ltr, rtl] layout direction service #1719

Closed
kara opened this issue Nov 3, 2016 · 4 comments
Closed

Introduce [ltr, rtl] layout direction service #1719

kara opened this issue Nov 3, 2016 · 4 comments
Assignees
Labels
needs: discussion Further discussion with the team is needed before proceeding

Comments

@kara
Copy link
Contributor

kara commented Nov 3, 2016

Similar to what the Dir directive does, but will also capture "dir" attributes outside the Angular app.

cc: @jelbourn

@kara kara added the discussion label Nov 3, 2016
@jelbourn jelbourn changed the title Introduce layout direction service Introduce [ltr, rtl] layout direction service Nov 9, 2016
@jelbourn
Copy link
Member

jelbourn commented Dec 9, 2016

@EladBezalel would you be interested in working on this? I have some thoughts in mind for it

@EladBezalel
Copy link
Member

@jelbourn sure! i'm always up to RTL stuff :D

@EladBezalel EladBezalel self-assigned this Dec 12, 2016
EladBezalel added a commit to EladBezalel/material2 that referenced this issue Dec 19, 2016
- Finds the application root element and traverses upwards and looking for dir attribute
- If Dir directive is available throughout the application it will be injected instead the activeLayoutDirection service

fixes angular#1719
EladBezalel added a commit to EladBezalel/material2 that referenced this issue Dec 26, 2016
- Finds the application root element and traverses upwards and looking for dir attribute
- If Dir directive is available throughout the application it will be injected instead the activeLayoutDirection service

fixes angular#1719
EladBezalel added a commit to EladBezalel/material2 that referenced this issue Jan 12, 2017
- Finds the application root element and traverses upwards and looking for dir attribute
- If Dir directive is available throughout the application it will be injected instead the activeLayoutDirection service

fixes angular#1719
EladBezalel added a commit to EladBezalel/material2 that referenced this issue Jan 12, 2017
- Finds the application root element and traverses upwards and looking for dir attribute
- If Dir directive is available throughout the application it will be injected instead the activeLayoutDirection service

fixes angular#1719
amitport added a commit to amitport/flex-layout that referenced this issue Mar 9, 2017
it is a very confusing mention of a directive that is not actually used in this demo.
Additionally, looks setting this on router root is likely to change (see angular/components#1719)
amitport added a commit to amitport/flex-layout that referenced this issue Mar 10, 2017
it is a very confusing mention of a directive that is not actually used in this demo.
Additionally, looks setting this on router root is likely to change (see angular/components#1719)
tinayuangao pushed a commit to angular/flex-layout that referenced this issue Mar 10, 2017
it is a very confusing mention of a directive that is not actually used in this demo.
Additionally, looks setting this on router root is likely to change (see angular/components#1719)
@EladBezalel
Copy link
Member

Simpler solution on #3600

karlhaas pushed a commit to karlhaas/flex-layout that referenced this issue May 3, 2017
it is a very confusing mention of a directive that is not actually used in this demo.
Additionally, looks setting this on router root is likely to change (see angular/components#1719)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
@mmalerba mmalerba added the needs: discussion Further discussion with the team is needed before proceeding label Mar 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs: discussion Further discussion with the team is needed before proceeding
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants