Bricks Version: 1.5.5 Browser: Opera latest OS: Win 11
Hi Team,
With custom breakpoints set (not sure if a factor or not). But I will be on the desktop breakpoint (Desktop first editing), and I will have ghosted values within margins, padding, sizing, etc. Although the editor did not show the applied ghosted value (which it wouldn’t if applied to a lower bp), dev tools do not show it, of course.
The obvious debug is to check the ID, the class, and the higher breakpoints from which it will have flowed down from. These were all clean. However, the ghosted values remain.
Found them on lower BPs which makes no sense to show the ghosted values on higher BPs.
I find values are NOT displayed while they are there. A bug which was fixed earlier.
So it displayes ‘nothing set’, yet a margin / padding / font-size / border / radius IS applied.
Meaning continuously searching where it is coming from.
Also seeing ‘blank fields’ where settings are applied, and even a ’ - ’ while the higher breakpoint’s margin is being applied.
I also noticed the same. Sometimes, I have even seen the padding fields go missing when I select the global class. I will take a screencast when I have time later.
Haha @jornes , I actually thought that was a new UI improvement they added that I had missed - this happens to me also all the time, constantly having to switch between class and ID I think this crept in on 1.5.5 too!
I’ve noticed that in my case, the grayed out number is nowhere to find. It’s not even hidden in a lower breakpoint nor the global theme settings, it’s simply not there at all. I just see random grayed out numbers all over the editor which is extremely confusing!
Hey @johannes@jornes, I think some that you find in elements will be hard coded for the elements to have a basic style, but I agree, it still throws you off, and you have to go and check everything to be sure.
I can confirm I have some presets in the theme setting. But some no(I will further investigate, anyway). But the padding/margin field missing when clicking on the global class is also the most frustrating.
Hey @Michael ,
Bricks 1.6 beta contains a fix for this problem. However, we would be happy if you could briefly test whether the problem is fixed so that we can include it in Bricks 1.6 stable.