www.wysiwygwebbuilder.com

Hello,

Doing a website here:

https://texasrosec2c.com/temp/about.php

Please view project-file download, here:

https://texasrosec2c.com/temp/proj.zip

When you load the .WBS file and navigate to "masterpage2" page, when you go into the 768 Breakpoint and the 320 Breakpoint, whenever you try to click and drag the Responsive Menu below about the 200 y-axis position to try to place it there, the Responsive Menu automatically "jumps back up" to the top of the page. Why is this? I need to move it underneath the logo for some designs I'm executing.

Is it the

STYLE >> Breakpoint
or
STYLE >> Full Width

settings or something..? I am beating my head against a wall.

God bless.

--etcbbu

Well I just copied the responsive menu and pasted it again and placed it below deleted the upper one and the result looks like this.

Note: I recommend to start using layout grids for responsive webdesign.

This is actually a 'safety' feature to make sure the menu does not get of the header, but currently it is a little but too sensitive. I will improve this in the next update.
In the meantime, you can use the workaround as described by 'wwonderfull'

Thank y'all, @wwonderfull and @Pablo!

I actually noticed this same thing was happening on *another* page in my project; but instead, with a "Layer" and with a ThemableButton object. Whenever I tried to click and drag the ThemableButton object and moved it onto a Layer I copy/pasted from another page. The weird thing is, again, it was only happening in the 768 and 320 Breakpoints.

So I just noticed when I deleted the Layer that was ding it, and just pulling-out a fresh Layer from the toolbox, redefined its parameters how I want it and the ThemableButton was "staying put", on this new Layer.

Just haven't seen this before and have done a number of WB projects. But who knows—maybe this .WBS file has a propensity for corrupting stuff in it. Maybe I'll try a Save As... and sort of "refresh it" to a new .WBS file of this project. I've been told / noticed sometimes that helps.

--etcbbu

Actually it is related to the height of the layer on the default view. That is what determines when the 'safety' kicks in.

Oh ok, on Layer objects and Page Header objects?

Yes, for all non-flexible layout containers.
This will be improved in the next update.