WIP: Table of contents Element: Highlighting does not work with position: relative

Bugs
1

Browser: FF 114.15.0, Safari 16.6.1
OS: macOS

When using the native ToC element, everything works fine except for assigning the active state to the current element. I found out that it has something to do with relatively positioned containers that contain my headings. Any heading inside a container that is ralatively positioned is not highlighted in the ToC, except the last one.

Is this behavior intentional, or does anyone have a workaround for me?

DUPLICATE: "Smooth scroll (CSS)" setting enabled causing inconsistent scrolling with Tabs (nestable) and Table of contents elements
DUPLICATE: "Smooth scroll (CSS)" setting enabled causing inconsistent scrolling with Tabs (nestable) and Table of contents elements
WAIT: Table of Contents (ToC) scroll offset incorrect when using "Smooth Scroll (CSS)"
WAIT: Table of Contents (ToC) scroll offset incorrect when using "Smooth Scroll (CSS)"
2

Hi,

I tested with relatively positioned headers and I could not reproduce your exact issue. I actually got one similar, where I could not select the previous heading of a relatively positioned one, so that will definitely go to the bug tracker.
But, I would also like to replicate your bug. Would you mind copy-pasting your structure/elements here, so I can test on your example?
If you want, you can also send it to the help@bricksbuilder.io, so we can take a look. If you will send an email, please also send a link to this thread.

Thanks!

Best regards,
M

3

Hi M,

I sent you an eMail with the Structure. Thx for your help.

Best,
Benjamin

4

As per our email conversation, I was able to replicate the bug and I added it you out internal bug tracker.

Best regards,
M

5

Hey Benjamin,
Sorry we haven’t been in touch for so long. We just came across a potential solution in this thread:

Have you enabled CSS smooth scroll in the Bricks settings? If so, could you try out the custom CSS fix and let us know if it resolves the issue?

The same goes for @dianaA and @blakmarkitcreative from the thread that was marked as a duplicate :v: Thanks in advance!