You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That seems inconsistent with what the docs say, or at least ambiguous:
controls whether or not to scroll a element (and its descendant elements) into view when after loading
I imagine the main case where a frame would be replaced outside the viewport is when a Stream makes an insert or modification, but with morphing that's becoming increasingly obsolete.
From what I see, that leaves a few options:
Remove the feature
Update the docs, or:
Enable the attribute to work regardless of how it got there
For turbo frame, autoscroll is usually used to scroll to the top of the frame, for example, if you have pagination implemented in a frame, when you click next page, the frame is updated and scrolls to the top of the results. I don't see how morphing would make this obsolete.
Docs can definitely be clearer about what "after loading" exactly means. It refers to loading the turbo frame, not just rendering it but actually performing a turbo frame navigation.
The text was updated successfully, but these errors were encountered: