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

fix(ripple): Ensure hover/focus states have proper z-index #2204

Merged
merged 1 commit into from
Feb 6, 2018

Conversation

acdvorak
Copy link
Contributor

@acdvorak acdvorak commented Feb 6, 2018

Previously, if the ripple surface had a non-statically-positioned child element (e.g., position: absolute), the hover/focus wash was displayed below the child instead of above it.

Previously, if the ripple surface had a non-statically-positioned child element (e.g., `position: absolute`), the hover/focus wash was displayed _below_ the child instead of _above_ it.
@codecov-io
Copy link

Codecov Report

Merging #2204 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2204   +/-   ##
=======================================
  Coverage   99.14%   99.14%           
=======================================
  Files          90       90           
  Lines        3843     3843           
  Branches      497      497           
=======================================
  Hits         3810     3810           
  Misses         33       33

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3ba2dc8...8ac142a. Read the comment docs.

Copy link
Contributor

@kfranqueiro kfranqueiro left a comment

Choose a reason for hiding this comment

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

Tested on top of #2039

@acdvorak acdvorak merged commit 751dabd into master Feb 6, 2018
@acdvorak acdvorak deleted the fix/ripple/z-index branch February 6, 2018 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants