When in mobile mode, when you click on one of the footer links to open the trigger works perfectly and the footer drop down menu opens as it should. However, when it closes the vertical axis for both the top and bottom appears to shift as does the link directly beneath it giving it a jerky reaction. Cannot figure out why as the states do not change at all. Any advice would be greatly appreciated.
Also, what youâre doing differently is clicking on the link to close it (which works fine) whereas Iâm clicking on the main header (i.e. Shop, About Us, etcâŚ) to close.
Ok I see, I olooked closely and donât get why it jumps.
However I donât understand why the dropdown elements need an interaction to ipen and close. By only passing the list position:relative, I got to design an accordion menu without any interaction there:
I was trying to get the links to open smoothly which is why I set the height to 0 initially within the interaction. The accordion you referenced is what I used initially but I wanted to add a bit of animation to get it to open gradually. See example 3 per the link below (click to show / hide content).
Hey @vinnie2727 I believe the jumpy part is happening because you have margin set on the Dropdown Footer Wrapper on both open/closed states. If you remove that margin then it behaves correctly. Please let me know if that solves is for you.
@Waldo that did the trick! Thank you! I canât believe I overlooked thatâŚ
Quick follow up question, can you try the footer on an actual mobile in portrait mode? There are a couple of issues that I donât see elsewhere (running Safari and Chrome on an IPhone 6).
When you click one of the footer links it momentarily flashes the link as if a hover / pressed state was set. Let me know if you see this as well.
More importantly, the menu items appear to load twice when you click a footer link (e.g. Shop). It loads, disappears quickly, and then loads again. This doesnât happen in any of the mobile preview modes on my desktop.
Glad it worked. I just took a look at your site in both Chrome & Safari on my iPhone 6 running the latest iOS and am only experiencing the issue in Chrome on iOS. Works perfectly in Safari for me. That is strange behavior in Chrome. Let me take a further look and get back to you @vinnie2727