'Scroll to section' to another page DOES NOT WORK

[Ben]

When a sublink from a header is configured to scroll to a section (block) on another page, it goes to the target page, but may not land on the targeted block. Since this has been an ongoing issue that builders have been wasting time configuring, perhaps Softr should remove the scroll to section feature when navigating to another page @artur?

Buttons on list details don't scroll to that list item's linked list

Instead, scrolls and opens up the first item on the linked list in your airtable view, like the default list order is in the studio.

'Scroll too' action on linked-list item button does not open in the same tab

… only opens in a new tab regardless of the setting, UNLESS THE BLOCK IS UPDATED. Glad the app I found this on is not published Again, if blocks eventually break when they get old, a better block update notification system should have been implemented already:

List block button doesn't scroll all the way

Apparently a list block item does not link to its corresponding listing details item if you set the button actions to ‘scroll to section’ rather than ‘open page’ on the list block. Can this be added to the studio if you want a list block item’s button to link to something else on its corresponding list details page (ex. a form block below the list details item?)

[artur]

@Ben, we are discussing this internally to either find a proper long-term solution or, as you suggest, stop that feature.

[Ben]

@artur, please let us know what you decide. It would be a useful feature, if it worked reliably.

[Ben]

@artur, there is still no change. Scrolling to blocks on other pages still renders unreliable landing points to the targeted block .

In the meantime, a suggestion would be to add a ‘Scroll to page’ option from blocks on details page buttons. We cannot simply scroll to the top of another page accurately from a details page right now.

[artur]

This week we are stabilising the order of blocks that are being fetched and rendered, afterwards we will look into section scroll… the challenge is our blocks load dynamically and scroll to section becomes non trivial as it needs to wait on the page for the blocks and their data to be loaded (included all data above the targeted one) and then start scrolling.

[Ben]

Okay. But in the meantime, could you add a “Go to page” action on a list details block button that simply sends the user to the top of a specified page? You have ‘scrolling to blocks on other pages’ that have never worked consistently anyway.

[artur]

Isn’t open page action doing exactly what you are asking ?

[Ben]

Yes, but from a details block the ‘open page’ only sends you to another details page, rather than any page like ‘scroll to’ action. So there’s no way to navigate to any other pages reliably from a details block. What if you want to navigate to a page, from a details block, that isn’t another details page?

[artur]

@Ben what about Open Url option ? It would though require you to link to a field coming from Airtable.

nevertheless I’m discussing internally to find a solution for link to other pages…

Question though if you take to scroll to page 1st block what is happening ?

[Ben]

Since scrolling to a block on another page does not reliably navigate to it accurately, the 1st block does not always scroll such that you see the entire block when navigated to. This has always been a problem with scrolling to any block on another page. In fact, it can send you to a random block on the target page at times too.

[acp73]

Also here because of this issue. When I first set it up a few months ago, I am sure it was working correctly & now suddenly no longer. Wold be great if this feature could be restored.

[Suzie]

Hey @acp73,

Please share a URL and mention the steps so that I can reproduce and share with the tech team if needed.

[artur]

Hi @Ben can you check if this is improved ?

[Ben]

Seems there’s improvement when scrolling to a block on another page, at least from the header today @artur. It doesn’t land at the same exact spot every time, but it does target the block it’s set for. As @acp73 mentioned, we’ll have to see how long this works and for which blocks apparently.

What did you change?

[artur]

We did logic to position better

[Ben]

Hey @artur. Looks like positioning was just improved. Scrollling landed slightly below the targeted block, which called for extra margin adjustments for it to land right with the content. Now it finally lands at the top of the targeted block. Nice!