"Add another" buttons could use vertical margin

Thank you for the interest @gaurav-mathur but screenshots were added in the comments before.

This adds some inconsistency to the spacing. This is quite visible on the top of the button. Ideally we would adjust the container margin to take this into account, but the form-action class is used elsewhere and I'm not sure how easy it would be for us to add additional classes there. It's important that the spacing on top of the button remains somewhat where it is now because that way we make sure that users associate it to the right element, and it doesn't look too separate.

Alternative solution we could try out is to handle this with margin-bottom, but that's likely not going to work because it will probably make the spacing on the bottom of the button inconsistent.

I've created a patch that applies to D10.2, it's kinda the same as #22, except it uses the margin-block instead of margin-top and bottom.

Hello @Arantxio,
Patch #33 applied successfully,The patch work properly.
please refer to screenshots.

This needs to be made against 11.x as the development branch. And need to make sure #31 is addressed.

Addressed #31 & #35.

I am trying to review this MR, but I am not able to add those buttons in my paragraph. I am using 11.x branch.

I am trying to review this commit on 11.x branch but I'm not able to reproduce the main issue.

Verified and tested after taking pull from this branch- 3198236-add-another-buttons. (#38) on the Drupal version 11.x. Its working as expected for the various themes.
Followed the below Testing Steps:
1. Install paragraph module
2. Create multiple paragraph types
3. Create a content type and add paragraph as reference field with 'Add mode' as buttons
4. Save the changes
5. Goto create content and check 'Add paragraphs' buttons have vertical margin
Attaching the screenshot for reference with various themes.
Hence moving it to RTBC
Thanks!

lauriii → closed merge request !5907

Committed e16d8e0 and pushed to 11.x. Cherry-picked to 10.2.x as a non-disruptive bug fix to Claro. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.