Skip to content
Create a gist now

Instantly share code, notes, and snippets.

BuddyPress Members directory
/*----------------------------------------------------------
Buddypress Legacy StyleSheet
------------------------------------------------------------
>>> TABLE OF CONTENTS
------------------------------------------------------------
1.0 - Members Directory
2.0 - Updates
3.0 - Pagination
----------------------------------------------------------*/
/*------------------------------------------------------------
1.0 - Members Directory
----------------------------------------------------------*/
#buddypress ul.item-list{
display: block;
margin: 0;
padding: 0;
}
#buddypress #members-list li.item-grid{
display: inline-block;
float: left;
list-style:none;
margin: 0 2% 1% 0;
vertical-align: top;
width: 48.65%;
}
#buddypress .member-avatar{
float: left;
margin: 0 3% 0 0;
}
#buddypress #members-list .member-single{
padding: 1rem;
overflow: hidden; /* temp fix */
}
#buddypress #members-list li.item-grid:nth-child(2n+2){
margin: 0 0 1% 0;
}
#buddypress .item-action{
float: right;
}
/*------------------------------------------------------------
2.0 - Updates
----------------------------------------------------------*/
#buddypress span.activity,
#buddypress div#message p {
margin-top: 3px;
text-decoration: none;
}
#buddypress span.activity {
display: inline-block;
padding: 1px 8px;
}
/*------------------------------------------------------------
3.0 - Pagination
----------------------------------------------------------*/
#pag-bottom{
clear: both;
}
@naton
naton commented Sep 26, 2012

Don't know if this it the right place for such comments, but adding a display:inline-block rule when there's already float is confusing (floats always causes display:block on an element). If browser compatibility is an issue, consider moving the float there to a file only accessed by browsers not understanding inline-block (and at the same time consider removing "rem" as a unit for the same compatibility reason).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.