Accordion in Webflow not working when a Finsweet Table is nested inside it

Description

When using Webflow Accordions if I add a Finsweet Table inside an Accordion it works fine. But I want to duplicate the accordion a number of times. When I duplicate it it doesn’t work. The accordion just stays open and doesn’t hide / show the nested Finsweet table as it should.

If you click the link the below and scroll to the bottom of the page you will see the accordions and the issue I’m having.

Site URL

Steps to Reproduce

  1. Click on The Annex Control Table Componant at the bottom of the staging link above.

  2. Duplicate Accordion Item FAQ

  3. You will see the Finsweet Table duplicated Accordion doesn’t work.

Expected Behavior

The Accordion should start closed and then when you click it it should open.

Actual Behavior

Accordion starts open and doesn’t work at all. Works for one accordion but not when duplicated

Video/Screenshots

Required: Please provide a short screen recording showing the issue

Additional Context

N/A

Thanks so much!

I really hope you can help.

Many thanks

Dave

Hey @design1! Could you share the read-only link to the project? I’ll take a closer look!

Hi Luis,
Sorry for the del;ay… here is the link

If you click on FAQs you’ll see the accordions are working fine. They are not working at all now on the accordions with the Finsweet tables in.

Hey @design1! I see the design has changed and the accordion now opens and closes with the table inside!

Could you pinpoint the issue?

Hi @Support-Luis

There’s still an issue. The accordions don’t work when housed inside a component. I’ve tried adding individual triggers on the other page and doing a close all accordions when page loads triggers but this just closes them and then they won’t open. See here:

The main page when the FIRST component was created is working fine though: The Ultimate Simple Guide to ISO27001:2022 Annex A

But when I copy and paste the component to another page they don’t work. We need to have these accordions on 90+ pages so they must be as a component.

Any ideas?

Thank you for the clarification @design1!

I have reached out to the team to see what we can do. Can you please sharea a page where the component is breaking? I was checking the first component which is the one that works correctly