Browser: Chrome 110
OS: macOS
URL: Link to a page that illustrates this issue
Video: watch my jam.dev
Hello,
I am encountering an issue with the “Read More” module in Bricks Builder. When a user clicks on an accordion to reveal hidden content, the page automatically scrolls to the bottom of that content, which creates a poor user experience.
Upon investigation, it seems that this behavior is related to a faulty implementation of the readmore.js library. On the official demo of the library, this issue is not present, so I suspect an implementation confusion within Bricks.
In the readmore.js demo page (Readmore.js), when you click on “Usage, examples, and options” to open the content, the browser does not scroll, but it correctly scrolls back when closing the content. However, in Bricks, the scroll occurs at the end of the opening, which force the user to go back to the top of the newly revealed content.
Is this a known issue, and is there a solution or a fix planned? If the bug persists, I may have to manually re-implement the library on each page because its my client that has found this UX issue.
Thank you for your help.
