New Bug in The Editor - Half Of Website is Not Visible

2025-03-30T22:00:00Z
Question:
Is this bug in editor happening to anyone else and how to fix this?

Product:
Wix Studio Editor

What are you trying to achieve:
I want to know if anyone else has experienced this recently.. Is this a problem on my behalf only or is this a new bug that more individuals are experiencing.. Also is there a fix?

What have you already tried:
Have tried contacting support, clearing browser cache and cookies, logging out of Wix Studio etc..

Additional information:
Hey friends, when I try to edit my website in the editor, a weird thing happens where the bottom half of my editor is not visible. Note, I have a custom breakpoint of 1920px width but this happens on all breakpoints. When zoomed in on 100% on 1920px breakpoint, it is visible just a slight bit on the bottom, but as I zoom out (Like I always design), you can clearly see that there is a blank line space separating the upper half of editor and the bottom half. The bottom half elements’ outlines are the only thing visible when hovering over some element. This hasn’t happened before ever and I don’t know why it started to happen. I haven’t made any recent changes that I know of in Studio that could cause this.. I will attach some screenshots and I am looking forward to any kind of help! Thank you in advance!


(unfortunately I can only attach one screenshot)

o meu esta acontecendo a mesma coisa e não tem ninguém no chat disponível para ajudar

That’s really unfortunate.. I can’t work on my projects because of this and it’s really frustrating

I have never used the zoom to reduce (design on a wide screen) but just tested and its working fine.
So may be a glitch.
Does adjusting the handles on the side to resize width reset it ? I cant replicate to do any problem solving sorry

@M.A.R_Solutions is this till happening for you? I know the team was working on a fix for something that may have been related to this - and might have been the cause?

If it’s still happening, I’d recommend reporting it as a bug here: