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

style(menu): apply theme bg color to menu panel rather than content #3941

Closed
wants to merge 1 commit into from

Conversation

willshowell
Copy link
Contributor

Previously, the menu's background opacity did not start animating until the menu had scaled to it's full size, despite the menu's drop shadow existing through the animation.

before-menu-light

Now, the menu's background opacity transitions in sync with the scaling. The content transitions in after scaling is nearly complete.

after-menu-light

[animations are slowed down 10x]

cc @kara

Previously, the menu's background opacity did not start animating until the menu had scaled to it's full size, despite the menu's drop shadow existing through the animation. Now, the menu's background opacity transitions in sync with the scaling.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 6, 2017
@willshowell
Copy link
Contributor Author

willshowell commented Apr 6, 2017

I now see that this was an explicit change made while adding animations, and that there is a similar convo about this breaking the spec with MdSelect.

Is there context that I'm missing? I've read over the design document and watched the official animations for menus and select and don't see where setting the panel background vs the content background is against spec.

@willshowell
Copy link
Contributor Author

@kara I'm interested in hearing your feedback on this

@willshowell
Copy link
Contributor Author

Closing due to change being made in #5361

@willshowell willshowell deleted the fix_menu_background branch July 10, 2017 13:05
@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants