SOLVED: CSS grid buggy and Uncaught TypeError?

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Link to a page that illustrates this issue
Video: Short screen recording that illustrates this issue (free tool: jam.dev)

Hiu guys

Having problems when clicking the CSS Grid and it’s not recognising the images and content in there after having set it up once. It goes default and I can’t see anything in the grid or change anything.

CSS Grid on the container shown:

What’s actually in Bricks:

Updates seem a bit sketchy too in the editor, where certain things like settings and CSS changes don’t reflect until a page refresh. Can’t show a direct e.g but it’s almost like something is jammed on the JS side, so some updates need a refresh to kick in. Seems to be mostly things like changing class names and not seeing the results until a refresh (possible BEM related on the ACSS tool).

lastly, I am also getting:

Uncaught TypeError: Cannot read properties of null (reading ‘parentNode’)
at HTMLDocument. (bricks.min.js?ver=1752851010:1:1716)

In the editor when editing.

Thanks

Ah, removing the container from a component seems to fix the grid. So this is an issue within the component.

That error comes from ACSS, not Bricks

Hi @robp,
Would it be possible if you can you send temporary login credentials to your website and a link to this topic to help@bricksbuilder.io using the email address you used during the purchase, so we can take a look?

Thank you,
Matej

Oh OK, good to know. Why’s it flagged in the Bricks file though?

Done this, thank you :slight_smile: I think most of the issues come with trying to edit inside a component. When I move things out of it again, then ACSS/BEM/copy&paste/updates, etc. all seem to work alright again.

It’s not - it’s an acss file

Maybe that’s jamming up some of the Bricks functions then, as I know ACSS doesn’t work well with Bricks components from my own testing.

Yup. Seems to me they didn’t adapt their scripts to 2.0 yet.

1 Like

Hi,

as I’ve already answered in the email, I can confirm that there is an issue with Visual Grid Builder inside the components. I’ve created internal task and I’ve linked this topic to it.

As the other issue mentioned here, it’s coming from ACSS like Maxime noticed, so it’s best to contact them.

Best regards,
Matej

We fixed this issue in Bricks 2.1 beta, now available as a manual download in your account (see changelog).

Please let us know if you are still experiencing issues.

As with any pre-stable release, please do not use it on a production website. It is intended for testing in a local or staging environment only.