Also if you can point out what is specifically different that would be very helpful, because at first glance I’m not sure what specifically you’re looking at and I’m not seeing anything that stands out as different visually, and I’d like to make sure we’re on the same page with what the problem is before I start hunting a solution. Screenshots or videos are always helpful.
I suspect this is just something to do with the Chrome browser’s responsive view. As when I view it on my iPhone, or in Safari’s responsive design viewer this does not occur. Both pages look identical. They even look identical within mobile Chrome on my iPhone. Give both pages a test on native devices and you should see them looking the same in both.
I am unfortunately not seeing any differences here in any browser or on any device I own. I’ll look closer at the stack, but there shouldn’t really be anything within the Badge Box stack that would affect the toggle for the Overlay Navigation.
You can’t affect the placement of that overlay toggle with a Margins stack.
OK, well, for your info the problem does appear on Android with this particular project. Once I’ve done with this one I’ll put together a really simple one and see if it still exists (it might be a combination of stuff on those linked pages). If it does I’ll let you know.
LOL, ya, sorry. Been a long day! I’m only trying Magallen as I can’t work out how the anchor stack works!
I have a contact form at the bottom of each page, I want various “Contact Us” buttons on the page to link to it, I want the page to scroll smoothly down to the contact form once click.
While I see the problem in your screenshot fine, I cannot replicate it here whatsoever. Without being able to replicate the problem that you’re running into, it is very hard to work on a solution. I will take a look at it as I said, but again, if I can’t make it have the problem here so that I can study and troubleshoot the problem, then it will take quite a deal of time to address it, if I can at all. It has been added to my internal issue tracker as of yesterday.
Yep, get that. And it was that about which I wasn’t sure. I understand you don’t have an Android device for real world testing, but wasn’t sure if you were able to at least see the issue in the Chrome Inspector. To be honest, I’m still not sure! I had several other people look at the pages in Chrome Inspect and they saw the issue, but I’m getting the impression it’s not happening for you? Can you confirm one way or another?
I didn’t realize you were wondering if I saw it in the device emulator mode of Chrome. I’d assumed we were talking about real world use cases. I can replicate it in the device simulator in the Chrome browser. But no where else. I am not sure that is a good test case or not comparative to a real device. I’ll keep it in mind for testing this problem.