-
Notifications
You must be signed in to change notification settings - Fork 772
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
The hover circle on material md-icon button is off when using fx-show / hide #105
Comments
Issues are considered invalid without a working Plunkr or CodePen demo. Also here are some important guidelines for investigating a Layout issue:
Templates |
Here is the plunker: |
@geelus - wonderful. we will investigate. |
I actually just ran into this myself, looking into what's stepping on the circle now. |
I fixed it by wrapping my button in a div and then applying the fxShow/fxHide to the div. |
@geelus - The difference between
While wrapping the element in a |
@d3viant0ne - fxShow/fxHide simply set the display to |
@ThomasBurleson - It's As you would expect, adding By default, it's applying the default for That brings up the question, is this really an issue with Also worth noting the scope of this goes beyond just //cc @jelbourn |
The fxHide and fxShow should not change the display mode to 'flex'. Instead the display mode (when not 'none') should be the default (=== 'block') or the explicitly assigned display mode for that element. @see https://github.com/angular/flex-layout/pull/121/files#diff-3600d4c60f78022f7136ec3b187f680dR126 |
The fxHide and fxShow should not change the display mode to 'flex'. Instead the display mode (when not 'none') should be the default (=== 'block') or the explicitly assigned display mode for that element. Fixes #105.
The fxHide and fxShow should not change the display mode to 'flex'. Instead the display mode (when not 'none') should be the default (=== 'block') or the explicitly assigned display mode for that element. Fixes #105.
@ThomasBurleson It doesn't seem to have been fixed in beta 3 or at least doesn't work for me. Can you please have this plunker working? |
@ThomasBurleson Thanks for clarification. So I'll check next version (beta 4) |
* fix(fxHide,fxShow): fix standalone breakpoint selectors * Many directive selectors were missing a `,` separator between then xs and gt-xs breakpoints * fxShow, fxHide preserve and restore the element's original display CSS style * added more tests standalone breakpoint selectors, disabled selectors, and deactivated mediaQueries fixes #62, closes ##59. * fix(api): add missing comma-delimiter in breakpoint selectors * add test to use md breakpoint via `fxHide.md` * fix(fxShow, fxHide): restore proper display mode when not active The fxHide and fxShow should not change the display mode to 'flex'. Instead the display mode (when not 'none') should be the default (=== 'block') or the explicitly assigned display mode for that element. Fixes #105.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
When using fx-show / hide in a md-icon-button, the hover circle is a few pixels off. Here's a screenshot:
![image](https://cloud.githubusercontent.com/assets/13104312/21785948/cd34151e-d715-11e6-8c4e-da68a79a647e.png)
The text was updated successfully, but these errors were encountered: