For the containerRelativeFrame, does that work cleanly in a List as well as a ScrollView?

The ability to get the id of the view at the top of the ScrollView is fantastic ❤️. Is there a way to do the same for the bottom?

I have a view with ScrollView and refreshable modifier. Most of the time it works fine, but sometimes, when a user performs pull to refresh, the content moves down, and doesn't come back. I have similar issue with refreshable but in my case the Large Navigation title jumps when pull to refresh is engaged.

Is it possible to position the content of a ScrollView by screen coordinates? I know it is possible to use scrollTo with the id of a view.

I’ve noticed that SwiftUI.ScrollView maintains @State as views are scrolled offscreen even when using Lazy views. That’s probably the correct behavior in most cases. But for very long lists, things like image assets and just general state can build up over time leading to performance and memory issues. What’s the best way to evict memory in this case?*

Is it true that you are adding Paging to scroll views in iOS 17?

Is the new operator .scrollPosition(id:) intended to actually scroll to a new position? In other words, is ScrollViewReader deprecated?

What is the best way to get ScrollView's contentOffset?

If we have a horizontal scroll view inside a list within a section, is there a way to make just that scroll view go end to end while the rest of the list get paddings?

What is the best way to know if a child view has been scrolled off screen as opposed to the parent view being taken off screen? (Basically different causes for onDisappear.) The best I've been able to find so far is using a GeometryReader and checking to see if the child view's geometry is within the parent's.