Skip to content

refactor(material-experimental/mdc-form-field): unset MDC custom baseline adjustment #18892

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

Conversation

devversion
Copy link
Member

@devversion devversion commented Mar 23, 2020

Recently with b2e8691, we updated to the latest canary version
of the MDC text-field. MDC updated how they align the input vertically.
We decided to still use our custom alignment using padding that will
also work for custom form field controls.

Since we still use padding alignment, we can unset the MDC
custom baseline styles. These currently have no effect, but
will cause the form-field to always have a minimum height that
needs extra treatment for the density levels.

Note: I will send an upstream PR on material-components-web. We should have more flexibility (individual mixins) for parts of the form-field. That should reduce unnecessary styles, and we should also not need any overrides.

…line adjustment

Recently with b2e8691, we updated to
the latest canary version of the MDC text-field. MDC updated how they
align the input vertically. We decided to still use our custom
alignment using padding that will also work for custom form field
controls.

Since we still use padding alignment, we can unset the MDC
custom baseline styles. These currently have no effect, but
will cause the form-field to always have a minimum height that
needs extra treatment for the density levels.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 23, 2020
@devversion devversion marked this pull request as ready for review March 23, 2020 13:41
@devversion devversion requested a review from mmalerba as a code owner March 23, 2020 13:41
@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels Mar 23, 2020
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added lgtm action: merge The PR is ready for merge by the caretaker labels Mar 23, 2020
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@andrewseguin andrewseguin merged commit f2d2c19 into angular:master Mar 25, 2020
@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 Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants