# 2 TOC attributes from the same content

**URL:** <https://forum.finsweet.com/t/2-toc-attributes-from-the-same-content/1618>\
**Category:** Attributes\
**Created:** [July 11, 2023, 6:16pm UTC](https://forum.finsweet.com/t/2-toc-attributes-from-the-same-content/1618 "2023-07-11T18:16:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fabien\_mnt](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/fabien_mnt/32/319_2.png) [@Fabien\_mnt](https://forum.finsweet.com/u/Fabien_mnt)\
**Post date:** [July 11, 2023, 6:16pm UTC](https://forum.finsweet.com/t/2-toc-attributes-from-the-same-content/1618/1 "2023-07-11T18:16:04Z")

</div>

Hello,  
I’m coming to you because I have a problem.  
I’m using the TOC in 2 places on the same page (1 on Desktop, the other on Tablet → mob).  
These 2 TOCs have the “fs-toc-element=link” attribute but work fine on the “fs-toc-element= content”. The problem is that the attribute only takes into account the first one placed on the page (which is on the tablet → mob version). This makes the attribute non-functional on Desktop.  
The workaround I’ve found is to add “fs-toc-element=link-1” and “fs-toc-element=link-2” but this forces me to duplicate the content (blog post) and hide/show according to versions, which is really not a good practice!

Here is a link : [Webflow - TOC Attributes test](https://preview.webflow.com/preview/toc-attributes-test?utm_medium=preview_link&utm_source=designer&utm_content=toc-attributes-test&preview=b2841e529bc6ca157efff925367fa891&workflow=preview)

Do you have a solution for this?

Thanks 😀

---

<div class="post-metadata">

**Author:** ![Support-Luis](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/support-luis/32/53_2.png) [@Support-Luis](https://forum.finsweet.com/u/Support-Luis)\
**Post date:** [July 11, 2023, 9:00pm UTC](https://forum.finsweet.com/t/2-toc-attributes-from-the-same-content/1618/2 "2023-07-11T21:00:50Z")

</div>

Hey @Fabien_mnt! I believe this might be one of the best approaches for this use case unless you might want to further style your components so they change positions on different breakpoints and only have one TOC instance.

I say this because I noticed the tablet TOC dropdown is a div with some interaction trigger to show and hide the actual table.