SOLVED: Social Sharing: margin on li with

Browser: Chrome 127.0.6533.100
OS: Windows

Hi bricks team,

If the website is RTL, according to the image below, the Social Sharing element has a 10px margin from the left by default. Now, if we set this margin to 0, it will cause horizontal scrolling in mobile browsers. But this margin does not exist in LTR.

I also have two requests from you about this element…

1- To create a gap between the icons, we need to go to style tab > gap. This is very far. If possible, please add the Gap option to the content tab of this element. It will be much faster to access.

2- An option to disable tooltip (data-balloon) on icons would be very useful.

cheers

This bug also occurs in LTR somehow.

1- Make sure the language of the website is LTR.
2- Add Social Sharing element to a container.
3- In the container settings, set Align cross axis to End. It will immediately appear in the horizontal scroll builder.

If you view the frontend on mobile, the horizontal scrolling is clearly visible.

Hi Hosein,
Thanks so much for your report!

I reproduced the issue with RTL and added it to our bug tracker. It’s basically the same issue as reported by yourself here: SOLVED: Bug in accordion element (in RTL) - #2 by timmse

You can easily fix it in the meantime with the following to get the same default styling as in LTR:

%root% li {
  margin: 0;
}

However, I can’t replicate any issue with LTR :thinking:

Best regards,
timmse

Hi timmse, Thanks for reply.

The css code you posted did not solve the overflow problem.

I don’t know why, but I have tested again now and there is no problem with LTR. I tested this item several times last night to make sure and then report!

Another similar case…

According to the screenshot below, the Nav Menu element has a 30px margin from the left by default. Both in RTL and LTR. Is this normal behavior?
If the margin is 0, but the gap is 30px, isn’t it better? Just like the top level in the nav nestable element.

thanks again

Yes, that’s the default setting. The gap setting was probably introduced much later, so it is difficult to set the margin to 0 and use gap as the default instead. This would probably lead to a “breaking” change for some/a lot users…

1 Like

Hi guys,

We’ve fixed this issue in Bricks 1.11 BETA, now available as a manual download (Bricks – Account)

Please let us know if you are still experiencing issues.

You can see the full changelog here: Bricks 1.11 Changelog – Bricks

As with any beta release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

Best regards,
Matej

Hi Matej, Thanks for the update🙏

This bug has been fixed but somehow there is still a problem which I have described here. (8 item)