-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
updated visibility classes to fall back to display inherit instead of…
… block. This fixes #887
- Loading branch information
Showing
2 changed files
with
13 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c562936
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zurbchris Why is Foundation changing an element's display? And
!important
? The previous version made a little sense (because it's understandable that perhaps Foundation can only do its "magic" on block elements), but when you change it todisplay: inherit !important
it makes clear that any type of display works (since the parent could have any display property).But adding
display: inline-block !important
to custom CSS overrides Foundation'sdisplay: none !important
, so the element never gets hidden.Edit: Wrapping the element with a parent of whatever
display
property is needed is one solution, though it's a bit hacky and doesn't explain the need for overriding thedisplay
property to begin with.