Over the past day or so, the Body frame has been showing misaligned in all of my projects. It doesn’t seem to affect the live site, but it is weird to work with.
Hi. I have discovered the same problem in ALL of my Webflow projects this morning and have identified the culprit. It’s the latest update to Chrome (Version 68.0.3440.75 on the Mac). Yesterday I noticed the body offset problem when I moved from my iMac, running Chrome 67, to my MacBook which was running Chrome 68. This morning I (stupidly!) updated to Chrome 68 on the iMac and voila, body misalignment issues. Darn it. Pic attached shows the issue for anyone interested.
I can confirm this is definitely a bug. I was running Chrome 67 with no problems at all. I upgraded to Chrome 68, the offset showed up. Just wanted to validate that this is a real issue. Thanks.
The body element in designer mode seems to be out of place, I’ve checked my other sites and it’s the same. Some sites have no classes added to the body.
Thank you again for reaching out about the body outline issue.
Our team was able to isolate the root cause of the issue and we’ve pushed a fix for this. It may still take some time for the new build to fully deploy, but the issue should be resolved this afternoon.
Can you please let me know if the issue is resolved on your end? If you still see this issue tomorrow, please let us know and we’ll reinvestigate this.
Thanks in advance!
Unfortunately I’m going to be away from my Mac all day tomorrow (Friday 27th July), but as soon as I get an opportunity to test, I’ll let you know the result.
Thanks for your super swift attention to the problem.
Any reason why the body is showing offset from the screen in designer? See screenshot. I can’t see any margins or padding that would cause this, and the outlines don’t seem to match up to the actual divs that are inside of them.
I’m certain you’ll have had this confirmed well before now, but as promised I can also confirm that the Body misalignment issue in Chrome 68 has been resolved - thanks to you and the team for addressing this issue so promptly. Here’s to Chrome 69!