Skip to content

fix(material/datepicker): support for date range input in MDC-based form field #22565

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

Merged
merged 1 commit into from
Apr 27, 2021

Conversation

crisbeto
Copy link
Member

Resolves a few issues that were preventing the use of the range picker with an MDC-based mat-form-field. Including:

  1. Conditionally setting the mat-mdc-input-element class so that the input is sized correctly.
  2. Triggering a state change event when the focus state changes so that the floating label is up-to-date.
  3. Fixing an error being thrown inside _shouldHideSeparator.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release labels Apr 26, 2021
@crisbeto crisbeto requested a review from mmalerba April 26, 2021 11:13
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 26, 2021
@crisbeto crisbeto changed the title fix(material/dialog): support for date range input in MDC-based form field fix(material/datepicker): support for date range input in MDC-based form field Apr 26, 2021
…orm field

Resolves a few issues that were preventing the use of the range picker with an MDC-based `mat-form-field`. Including:
1. Conditionally setting the `mat-mdc-input-element` class so that the input is sized correctly.
2. Triggering a state change event when the focus state changes so that the floating label is up-to-date.
3. Fixing an error being thrown inside `_shouldHideSeparator`.
@crisbeto crisbeto force-pushed the mdc-form-field-range-input branch from 7425147 to d12eb89 Compare April 26, 2021 11:17
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

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Apr 26, 2021
@andrewseguin andrewseguin merged commit 355233d into angular:master Apr 27, 2021
andrewseguin pushed a commit that referenced this pull request Apr 27, 2021
…orm field (#22565)

Resolves a few issues that were preventing the use of the range picker with an MDC-based `mat-form-field`. Including:
1. Conditionally setting the `mat-mdc-input-element` class so that the input is sized correctly.
2. Triggering a state change event when the focus state changes so that the floating label is up-to-date.
3. Fixing an error being thrown inside `_shouldHideSeparator`.

(cherry picked from commit 355233d)
andrewseguin pushed a commit that referenced this pull request Apr 27, 2021
…orm field (#22565)

Resolves a few issues that were preventing the use of the range picker with an MDC-based `mat-form-field`. Including:
1. Conditionally setting the `mat-mdc-input-element` class so that the input is sized correctly.
2. Triggering a state change event when the focus state changes so that the floating label is up-to-date.
3. Fixing an error being thrown inside `_shouldHideSeparator`.

(cherry picked from commit 355233d)
@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 May 28, 2021
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 P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants