#item-header should not use `overflow: hidden`

[r-a-y]

Here's an example why we shouldn't use the CSS overflow: hidden declaration for the item-header DIV:

The BP Group Email Subscription plugin adds a <div> in the group header that gets cut off because of the hidden declaration.

Attached patch fixes this by removing the overflow: hidden declaration and replaces this with a clear: both declaration via #item-header:after.

[imath]

Nice catch again! Looks good to me.

[hnla]

@r-a-y We should implement a bp-clearfix class really, then can just add the class where required on new elements or old.

[r-a-y]

We should implement a bp-clearfix class really, then can just add the class where required on new elements or old.

For sure, but buddypress.css doesn't use SCSS ;) (Sounds like a good enhancement ticket!)

Feel free to go with this with the companion stylesheets though, hnla!

[hnla]

Doesn't matter about scss though, we just add a class (ruleset). The best place for that would be located in the main styles rather than the companion styles.

It's partly as I have a concern that clearing is getting a little complicated, I noted that the cover image styles are running some clearing on the item-button div that might be better handled.

[r-a-y]

In 10289:

bp-legacy: Do not use overflow: hidden for #item-header DIV.

Fixes a potential issue with truncated content. To be extra safe, we're
clearing the #item-header DIV after it is rendered with the :after CSS
property.

Fixes #6672.

[r-a-y]

Doesn't matter about scss though, we just add a class (ruleset).

Oh, I was thinking we'd use a sass mixin to avoid having to add the bp-clearfix class to the markup.

I noted that the cover image styles are running some clearing on the item-button div that might be better handled.

Where are you seeing this?

[hnla]

Where are you seeing this?

On the cover images header groups iirc, on the embedded styles for the cover images, did discuss with Imath briefly who leaves it in our capable hands :)

We have overflow handling clearing then pseudo element :before adding content whitespace, it either needs to be overflow to hadle containment or a full clearfix ruleset.

Oh, I was thinking we'd use a sass mixin to avoid having to add the bp-clearfix class to the markup.

Yep good point and probably would if we used scss for the main rules, however I tend not to like that approach as it starts to pad out the stylesheet, adding classes to markup tends to be lighter - as long as can add safely :)