SOLVED: display: none hides element from structure panel

Bricks Version: 1.4.0RC
Browser: Firefox Dev
OS: Windows 10

Hi,
if I set a section to “Display: none”, the section disappear from the structure panel. Se the two screenshot below. Here, the section is visible.

And here I hide it. The problem is that if I close left panel not, I will not be able to edit/select this anymore. To edit it, I would have to go to developer tools, change CSS there to become visible and then I could click on it in the builder. Which I guess it is not intended way to do it :wink:

This is the section that I imported from my templates, if this helps.

Regards,
Matej

Weird, if I set display: none, the element remains in structure panel but with a little icon (“hidden”) on the right:

image

Interesting. I see that on my 1.4RC site that I upgraded from 1.3.6 it happens always on any element, but on new site, on which I started working on with 1.4RC, it behaves correctly, as on your site.

I’m starting to wonder if there is a settings somewhere that could cause this?

Not to my knowledge, and I did nothing special :wink:

Yeah, probably is some error, maybe because of upgrading? Lets wait for the devs to confirm it :smiley:

Hi Matej,
Thanks so much for your report!

Unfortunately, I am not able to reproduce the issue, even with an updated site.
After updating, did you run the converter (Bricks » Settings » Convert)? If not, please do it and let me know if it fixes the issue.

Best regards,
timmse

Hi,
sorry for my late replay. I look around to what would cause this and the problem is again in another plugin. For the forms plugin, I have “Bit Forms” installed and they have .hidden class, with !important and it gets applied to your element on the structure pane on the right.
slika

Even if there is no !important, the element on the right is hidden.

Sorry if I cause you too much trouble with this. Do you think I should contact Bit Forms developers now and they can correct it, or is this something you could do? I think this should be corrected on Bit Forms side?

Matej

This should definitely be corrected on the BitForms side…they should never be using a class as generic as that, and definitely not with !important

1 Like

Yeah, I taught so. I was also surprised that they used !important. I am definitely not fan of it. I will contact their support.

WSForms is high recommended!

I know, but for what I need, Bit Forms was enough and quite simple to use. And of course, the pricing is better on Bit Forms.
I also have Piotnet forms, but I found that UX for creating forms is too clumsy to work on them.

Hi Matej,
oh my gosh… :see_no_evil:

I agree 100% with Eric!

Best regards,
timmse

Just to update for all that might be reading this in the future, Bit Forms issued an update and it solved the problem. It all works perfectly now :slight_smile:

2 Likes

Hi everyone, quick question. If this question is irrelevant to this thread please let me know so I can post it in the appropriate thread. When we use the display none in Bricks do the elements get rendered in the front-end with the css display:none property or do the elements actually not even render? If so what is the best way to disable elements from completely rendering on the front end?

Hi.
When you use display:none, the element will render on the page, but it will not be visible. If you don’t want to render elements on the page at all, you will need to set conditions (Element Conditions – Bricks Academy)

Ah, so the display options in Bricks is actually a CSS parameter then. Thanks for clarifying that. I’ve been primarily using the drop down options and setting it to “none” in the context of mobile usage. So Element A for example can be shown on the desktop but not on mobile. However, from what you’ve said Element A is still going to render on mobile but it will be set to display:none. There are no conditions I can use to set Element A to not render on mobile so I guess using display none is the only option. Is that a good practice?

Yep, this is the correct way. Just hide the components with CSS for mobile.
You actually can’t set conditions for elements to not render on mobile, because server doesn’t know the screen resolution. :slight_smile:

So, feel free to use it like you use it now :wink:

Awesome! Appreciate the support!