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

md-input-container: mdPrefix and mdSuffix divs should not be present when there is no content #3659

Closed
natsid opened this issue Mar 17, 2017 · 2 comments · Fixed by #3724
Closed
Assignees
Labels
P2 The issue is important to a large percentage of users, with a workaround

Comments

@natsid
Copy link

natsid commented Mar 17, 2017

Proposal:

I'd like to propose adding an ngIf on both the .mat-input-prefix and .mat-input-suffix divs in the md-input-container template so that they are only in the DOM if the user has included a prefix/suffix.

What is the use-case or motivation for changing an existing behavior?

I'd like to be able to add space between the infix and the affixes, but only when an affix is present.

What is the current behavior?

Currently, if I add any sort of spacing there, the space shows up even without the affix, as seen in the second input here.

@jelbourn jelbourn added the P2 The issue is important to a large percentage of users, with a workaround label Mar 21, 2017
@jelbourn
Copy link
Member

I agree that we should only render those elements if the directives are present.

@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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants