Hi - I've been sort of missing in action for the last year or so and haven't really kept up with the changes from v3 to v4 to v5.

Trying to catch up, get back to speed - running through the Vision Tutorial. On the nav-wrapper - using the Foundation mobile first blank template. I created the nav bar - it looked fine, like the illustration. Then working thru to the responsify section of the tutorial. I set the slider into the second break point (beyond the mobile point). I change the display layout to flex and follow the directions - it's appears to be all good. However, when I return to the mobile (left of first break point) - now that is ALSO flex row... no longer block. If I change it in mobile to block, then go back to middle break area and change that to flex, save, and reload the file, then bring it up - mobile is STILL flex? v5 build 3360 Windows version.

I would have thought (and would have preferred) that the mobile remain links being page width, then second break (media width) and beyond be flex. I don't know though, whether flex is global or whether something has gotten corrupted in the file or ????

It seems possible that it's to do with the setting of 'Toggle Breakpoints'. While it's set to 'Disable All Breakpoints', no matter where the slider is, every change is treated as below the first breakpoint. Setting it to 'Default Mode' should make the settings at different breakpoints happen as expected.

Frank

Thank you Frank! That was an application setting that I hadn't noticed - yep that fixed the issue I was experiencing. Not sure why Site Designer installed with that defaulted to disable all breakpoints - I even uninstalled and reinstalled thinking something might have gotten tweaked. I was on the verge of working out a javascript that triggered onload to alter the display property depending on the value set by a media query or perhaps make two menus with two different class ids and settings - set one to the appropriate display value, the other to none (hidden) - cumbersome and prone to randomly not working depending on client browser issues. YUK!!!

Thanks again! You saved me from wasting considerable time!

Sincerely,
Gordon Lincoln

It is indeed ironic that what is called 'Default Mode' is in fact not the default setting. Perhaps some rethink of the terminology is needed. Even the word 'Toggle' in the button's title doesn't seem really appropriate.

I do, however, think that the current default setting probably is wise for new users. It prevents the mess that occurs by making beyond the first breakpoint (mobile first) style settings intended for all breakpoints.

Frank