Maybe another editor bug? Empty space related

page is this .
pw is pw4GOLIVE
Site name is houth1
scrnsht below

Problem is: Giant empty space where the box is supposed to be despite it being fully collapsed, footer is beyond viewport on load on a 24" monitor.

dont mind the messy box, like i said i am actively playing with it :), but there is a box and a bunch of content on it and there will be similar boxes as you can imagine (i decided to use boxes instead of a slideshow, nevermind the why haha)


THANK YOU!

Have you read about the 70 pixel rule?

Hay Omid,

I have forwarded this case to the dev team to explain what is going on. As far as I can understand, the footer should have moved up to be in the viewport.

Thanks!

Would you happen to know if the fix to this will apply site-wide by any chance?

Hay Omid,

There are a few things you can do to solve this -

  1. In some of the elements you are using hide and not collapse. You should use collapse.
    Hide preserves the vertical space, while collapse removes it. The criminal defense box is set as hidden, not collapsed, as a result the footer will not move up.

  2. Another reason the footer does not move up is because of the footer was set to a specific position using the resize handle. If you drag the footer down manually, it will not move up because of collapsed elements.

To reset the footer, so that it will adjust to the site content, just double click the footer resize handle.

Checkout the pic below -
we show three cases

  1. the box is hidden - footer does not move up
  2. the box is collapsed - footer does move up
  3. the box is collapsed, but the footer was dragged down first - the footer does not move up

You rock!

Ok so, to confirm, even though my box was both set to hidden AND collapse, the hidden attribute cancels out the part of collapse function that would not waste the space, and causes it to actually preserve the empty space, right?

Also, on #2, is that a PER PAGE thing? Meaning, if I have moved the footer manually on any of the pages, will this collapse non-compliance on all pages or only on that one page-assuming one has collapsed items on most if not all pages in a hypothetical case, fore educational purposes :slight_smile:

I will play and get it right, but I just know I shall forever remain a noob when it comes to these new combos of attempts haha I have to play and find out the hard way usually.

Ok, so I just tried on the same page and set all my 3 long boxes to only collapsed on load, unchecking hidden box. I have also ensured the footer is not manually moved around, but the space still persists. Could there be something else? Or am I not doing something right here. I made sure to pull the footer all the way to line up with bottom of my longest box, then pushed that box down, and then pulled it back up, pulling up the footer with it. But the end results so far have not changed.

Ok, so testing this, I can report a couple irritating issues:

Right now, I have 3 boxes with different lengths on top of one another that will appear and disappear via collapse/expand. I made sure the footer was aligned to the bottom of the tallest box, but then when I cut that box out the footer did not auto-collapse to the bottom of the next tallest box. I had to again manually pull it up. I had already pulled up my tallest box to Y @ 0 earlier…

Ok, now to fix this, I can see I need to CUT (CTRL+X) my boxes, pull the footer all the way up, and then paste back my elements. Herein lies a HUGE FLAW. Everytime I do this, ALL my element properties and on-click on-hover conditions disappear from the elements properties panel themselves. The names remain, but all conditions go away. The code custom made for the page or site remains in relation to the now-gone per-element condition. This requires me to go in and manually redo all of those for something like 50 different items on a rather specifically designed in such a way page for my own reasons.

While we are this, could this matter for properties be reported as a feedback/bug and be fixed so these resets do not occur? Evidently this is going to happen during experimentation and design process at least once to each user and it is a miserable experience, considering I have already had to do this once before yesterday and learning the hard way…

Similar properties reset occurs when you duplicate a page or a group of such conditioned elements… the custom code gets duplicated but it wont work until you go in and manually reattach all those disappearing properties.

Name remains, checkboxes for hidden/collapse remain, but all mouse-related conditions disappear underneath those in the properties box

Please kindly note, I am not trying to complain or sound so. These are just reports of my experience and issues as I put myself in shoes of your average user and see how “stuck” or “defeated” they may feel when they run into such situations. I was able to solve mine with minimal casualties by doing the CTRL+X to only my lowest of all items in the tallest of all boxes before I got the desired end results with footer moving into the viewport on load. It literally took 1 min after the above post to figure this compromise out.

But fixing these sorts of UX matters even on the Code platform that is geared towards the more adept users can imho greatly reduce support pressures and costs and improve sentiments and further your britlliant minimally-costing marketing strategy. I follow those investor relation and press release items from time to time :wink:

Hay Omid,

Wow, that’s a long thread…

You do not need to cut the boxes of the page to drag the footer up. You can just double click the footer resize handler and that resets the footer to auto resize based on the page content.

And the footer position is per page, not global among different pages.

Sorry, rushing through this today facing a deadline. I must have missed the double click bit for footer to come up :confused: dangit. my bad.

Your solutions do not seem to work on my site, is it simply impossible to utilize more than 70px of space on collapse?

Here’s my Site: https://byron062.wixsite.com/devmode
Please advise thanks