Community forum for knowledge and support

Updated 2 months ago

Header-103 Issue with Tab Navigation

At a glance

A community member is using a "header-103" component on a client project, and the tabs keep skipping to the front instead of working through them one by one. Other community members try to help by asking for more information, such as the browser used and providing staging links. However, they are unable to reproduce the issue and suggest the community member try a different component as a workaround while they investigate further. There is no explicitly marked answer to the issue.

Useful resources

Hey guys, I am using "header-103" on a client project, and each tab keeps skipping to the front rather than just working through them one by one. Has anyone else had this issue?

M
S
J
17 comments

@Sam Passmore how long ago did you paste in the component? What browser? Can you send a staging link (webflow.io)?

Hey @Matt, I pasted this in almost straight after the comment. Probably about an hour after. Here is a staging link - https://gel-website-92f0cc.webflow.io/

Hey @Matt just wondering if you had any updates on this? Ive tried in Chrome and its exactly the same

@Sam Passmore I seem to remember something like this in the past - I'll have to dig into it a bit. As you can imagine, not an easy fix.

@Sam Passmore just in case, can you pass along the read-only link as well?

yeah its very strange, it works fine when I paste it into a project:
https://jan-6th-feb-3rd.webflow.io/

Which I know is not super helpful, but it is a bit hopeful that it should work or at least does work.

That is so strange. Keep me updated if you find a fix. I haven't changed anything in the code embed.

Hey @Matt is it not looking like we can get a fix on this? Im using it on a client project that goes over for review this week.

Hey @Matt, sorry for pestering but if we cant find a fix I will have to rethink the hero section. Could you let me know if this is something we don't have a fix to?

@Sam Passmore sorry Sam, its working fine for me in Safari and the original component also works. Its very very difficult to track down a bug that is not easily reproduced. If I could reproduce it or follow any steps to reproduce it, I'm sure we could have it resolved in a couple of hours. With all that saying, i would go with plan B of swapping the component for now while we try to create a path to reproduce this issue.

Thanks Matt. Appreciate the response

yeah bummer though, I'll try to circle back around to this.

Hi all! Any fix in place for this? I'm running into the exact same issue. Just copied the component today.

@John DeMarchi can you provide the webflow read-only link as well as the published URL (webflow.io)? And what browser are you testing this in?

Hi @Matt ! I don't have client consent at this time to share a link. But I did some further digging last night and may have figured things out.

I rebuilt the component from scratch using an empty webflow page and newly copied Relume components (including the full page structure). And… voila! It's working.

In my first attempt, the page where I was placing the component does not have the full page structure in place. My best guess is that is what may be causing the problem. Does that sound feasible? If so, that may be useful information for anyone else running into this issue.

Add a reply
Sign up and join the conversation on Slack