Ok, sure.

Just for the record, meeting and proposals (and most of the resources) use the layout_item type, however, blogs do not. Blogs is using the layout-1col (as the most of the forms, but not the resource items). Therefore, it does not apply the same section/spacing stuff, i.e the css behind the scenes is different.

I'll make equal both gaps, good catch! :)

That issue is due to the endorsers_list cell. Notice that the resources you say they're OK, have no Like button. This cell comes with three things:

• The button Like itself.
• The small version of the endorsers list (up to 3 elements). It acts like the trigger to the full endorsers list.
• The full endorsers list.

Big deal here is the endorsers_list. It is hidden until you click the small version of the list, but it cannot be absolute positioned since it comes: first, horizontally aligned with the tags in desktop but not in mobile; second, it could grow as much as it wants (i.e. many endorsers) overlapping the comments section.

An easy solution (workaround) that comes to my mind now would be to increase the gap a lot. Similar to the current debates page. Doing this, you could add quite a lot endorsers "safely" (but the issue stills). Thoughts?

An easy solution (workaround) that comes to my mind now would be to increase the gap a lot. Similar to the current debates page. Doing this, you could add quite a lot endorsers "safely" (but the issue stills). Thoughts?

I'd prefer to have the three of them as the Proposals/Posts page, as Debates is too big the gap.

Also the solution of "let's add more space" doesn't work well, as we don't know how many endorsements could be there. For instance, generating multiple Endorsements I can make this gap big in a Proposal:

As a participant, it doesn't make sense to have this gap.

It only makes sense when we open the endorsers list:

You can reproduce it locally with this small snippet:

resource = Decidim::Endorsement.first.resource

Decidim::User.all.each do |author|
  Decidim::Endorsement.create!(resource:, author:)
rescue StandardError
end

And then visit the page of this resource.

As that's not a quick fix, I propose to:

1. As I said before: to have the Debate page with the same gap as Proposals/Posts, so we can merge this, as it's fixing the issue of consistency between the margin of the different resources
2. To create a new issue with this new bug ("margin for comments grows when there are lots of likes").

As I said before: to have the Debate page with the same gap as Proposals/Posts, so we can merge this, as it's fixing the issue of consistency between the margin of the different resources

Uff, that's problematic. Debates is OK, as uses the same layout as the rest of the resources. The issue comes when the content is smaller than the aside. Look at the following screenshot:

Since the layout item is a grid, when the aside block is larger than the main content, it forces this one to stretch. Once the main content includes more text, such gap comes back to "normal".

So, that big gap will come up always that the main content is smaller than the aside block.

Uff, that's problematic. Debates is OK, as uses the same layout as the rest of the resources. The issue comes when the content is smaller than the aside.

Ah Ok, I thought it was something weird happening here but I can see the same behavior in other resources too as you mentioned.

Adding the no-backport label as this isn't happening in v0.27

As this is assigned to @alecslupu and he already gave a review, he'll have the final merge power on this PR.