WIP: Two issues in Components (in builder)

Bugs
1

Browser: Chrome 131.0.6778.205
OS: Windows

Hi bricks team,

1- If we use Components in the header or footer, we will experience a sharp page jump when selecting it in the canvas. This bug seems to be related to this.

Please watch the video below. If we use elements other than Components, we will not have any jumps, but in Components the situation is different and there is a lot of jumps.

2- There seems to be a problem between Components and Cascade layer.

2

Regarding the first one, there seems to be a related issue that only occurs in the WooCommerce dashboard. But there is no issue in the endpoints. Please watch the video below.

3

Hi @HOSEIN,

I was unable to replicate the issue :frowning: But, I was using my “button” component to test, and it looks like this is happening only if the component is some kind.

Can you export both components that you used, so I can test them?

Thanks,
Matej

4

Hi Matej,

Before the component, I just used the button to make it clear that it would be okay if I used a button or any other element.

Have you tried the component in the header or footer? This bug only occurs in the header and footer.

5

Hello @HOSEIN,

thank you for the component. I was able to replicate first issue locally, and I’ve added it to the bug tracker.

But for the second one, I was not able to replicate it, so I’m wondering if you have the page online, where I can check one page where it works, and Woo dashboard, where it’s an error.

Thank you.
Matej

1 Like
6

Hi @Matej,

Please login here.

After logging in, if you look at the header elements, the icon size in them is very large. But if you go to the orders tabs, etc., they return to normal.

7

Thank you @HOSEIN,

I was able to reproduce also the second one, and I’ve added it to the bug report. It was a combination of External CSS files and icon elements on a page in addition to the header. :slight_smile:

Thank you,
Matej

1 Like
8

Hi @HOSEIN

We’ve fixed the second issue in Bricks 1.12, now available as a one-click download from your dashboard.

Please let us know if you are still experiencing issues.

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

Best regards,
Matej

Best regards,
Matej

9

Hi Matej,

Thank you,

If you agree, I think it would be better for me to separate the first issue from this report and create another report for it?

10

Hi @HOSEIN,

for now, I think it’s not needed. Once we also solve the first issue, we will change it to “solved”. But, maybe for next reports, if the issues are not the same, let’s create own forum posts :wink:

As you can see, it’s much easier to handle solved/wip reports that way :slight_smile:

Thanks,
Matej

1 Like