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

feat(autocomplete): align with 2018 material design spec #12570

Merged
merged 1 commit into from
Aug 17, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Aug 7, 2018

Aligns the autocomplete with the most-recent Material design spec. These changes are based on the menu designs since there isn't any concrete design for an autocomplete. Note that the changes only cover the adjustments to the autocomplete panel. The design changes for the options will come together with mat-select since the two components both use mat-option.

angular_material_-_google_chrome_2018-08-07_21-08-33
angular_material_-_google_chrome_2018-08-07_21-38-51

@crisbeto crisbeto added the target: major This PR is targeted for the next major release label Aug 7, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 7, 2018
@@ -579,6 +579,13 @@ export class MatAutocompleteTrigger implements ControlValueAccessor, OnDestroy {
{originX: 'start', originY: 'top', overlayX: 'start', overlayY: 'bottom'}
]);

this._positionStrategy.positionChanges.subscribe(({connectionPair}) => {
Copy link
Member

Choose a reason for hiding this comment

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

Add a comment here like...

// The overlay edge connected to the trigger has squared corners, while
// the opposite end has rounded corners. We apply a css class to swap the
// border-radius based on the overlay position.

Alternatively, since this seems to be a common pattern, what do you think of adding a panelClass property to ConnectedPosition (to be applied when that position is used)?

Copy link
Member Author

@crisbeto crisbeto Aug 8, 2018

Choose a reason for hiding this comment

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

I've included the comment and I've left a note for myself to add a panelClass to the ConnectedPosition.

Aligns the autocomplete with the most-recent Material design spec. These changes are based on the menu designs since there isn't any concrete design for an autocomplete. Note that the changes only cover the adjustments to the autocomplete panel. The design changes for the options will come together with `mat-select` since the two components both use `mat-option`.
@crisbeto crisbeto force-pushed the autocomplete-new-spec branch from 88566a8 to a82ffe8 Compare August 8, 2018 19:10
@crisbeto crisbeto changed the title feat(autocomplete): align with 2018 material design feat(autocomplete): align with 2018 material design spec Aug 10, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 10, 2018
@ngbot
Copy link

ngbot bot commented Aug 10, 2018

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure status "continuous-integration/travis-ci/pr" is failing

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@jelbourn jelbourn added the P2 The issue is important to a large percentage of users, with a workaround label Aug 14, 2018
@mmalerba mmalerba merged commit b9651df into angular:master Aug 17, 2018
@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 9, 2019
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: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants