Skip to content
This repository was archived by the owner on Jan 6, 2025. It is now read-only.

fxHide breaks style of non-"display: box" elements #141

Closed
netmikey opened this issue Jan 29, 2017 · 4 comments · Fixed by #143
Closed

fxHide breaks style of non-"display: box" elements #141

netmikey opened this issue Jan 29, 2017 · 4 comments · Fixed by #143
Assignees
Labels
bug has pr A PR has been created to address this issue P0 Critical issue that needs to be resolved immediately
Milestone

Comments

@netmikey
Copy link

As part of a responsive UI, there are times when we want to hide some elements of our UI (not whole parts, just a bunch of elements e.g. an item's label) on small screens.

As an example, I'd expect the following to work so that on non-xs screens, it displays the label inline next to the icon, and on xs screens only the icon remains:

<div>
    <img src="icon.png">
    <span fxHide.xs>Label</span>
</div>

The show/hide functionality now works as of v2.0.0-beta.4, but it looks like it toggles only between display: none and display: block, ignoring the actual display mode the element was in before fxHide got applied.

I think fxHide should take into account the element's actual display mode and not interfere with it.

ThomasBurleson added a commit that referenced this issue Jan 30, 2017
*  fxShow and fxHide should restore original display modes when deactivating
*  combination uses of fxHide + fxShow should work properly
*  static uses of `fxHide=""` should hide the hosting elmement

fixes #140, fixes #141.
ThomasBurleson added a commit that referenced this issue Jan 30, 2017
*  fxShow and fxHide should restore original display modes when deactivating
*  combination uses of fxHide + fxShow should work properly
*  static uses of `fxHide=""` should hide the hosting elmement

fixes #140, fixes #141.
ThomasBurleson added a commit that referenced this issue Jan 30, 2017
*  fxShow and fxHide should restore original display modes when deactivating
*  combination uses of fxHide + fxShow should work properly
*  static uses of `fxHide=""` should hide the hosting elmement

fixes #140, fixes #141.
@ThomasBurleson ThomasBurleson added bug has pr A PR has been created to address this issue labels Jan 30, 2017
@ThomasBurleson ThomasBurleson self-assigned this Jan 30, 2017
@ThomasBurleson ThomasBurleson added this to the v2.0.0-beta.5 milestone Jan 30, 2017
@ThomasBurleson
Copy link
Contributor

Fixed in PR #143

@ThomasBurleson ThomasBurleson added the P0 Critical issue that needs to be resolved immediately label Jan 30, 2017
ThomasBurleson added a commit that referenced this issue Feb 2, 2017
*  fxShow and fxHide should restore original display modes when deactivating
*  combination uses of fxHide + fxShow should work properly
*  static uses of `fxHide=""` should hide the hosting elmement

fixes #140, fixes #141.
ThomasBurleson added a commit that referenced this issue Feb 2, 2017
*  fxShow and fxHide should restore original display modes when deactivating
*  combination uses of fxHide + fxShow should work properly
*  static uses of `fxHide=""` should hide the hosting elmement

fixes #140, fixes #141.
@kara kara closed this as completed in #143 Feb 2, 2017
kara pushed a commit that referenced this issue Feb 2, 2017
karlhaas pushed a commit to karlhaas/flex-layout that referenced this issue May 3, 2017
@netmikey
Copy link
Author

netmikey commented May 26, 2017

It looks like this still happens (or maybe happens again?) in Firefox 53.0.3 with v2.0.0-beta.8:

When I add fxHide.xs to an element that has display: flex; applied in the css file, on Firefox it injects style="display: block;" in the dom, overriding the css. On Chrome, it doesn't inject anything.

@ThomasBurleson
Copy link
Contributor

ThomasBurleson commented May 27, 2017

@netmikey -

  • please provide a demo reproducing your issue
  • please do not cc people in your comments.

@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 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug has pr A PR has been created to address this issue P0 Critical issue that needs to be resolved immediately
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants