Just a quick reply -- I'll put together a sample project for the feedback report and have it for you tomorrow (Wednesday). I am using Xcode 16.4 running on macOS 15.7 working with a project where the Minimum Deployment Target is iOS 18.0 (I changed it from 17.0 to try using the .onScrollGeometryChange API). I see the problem (i.e., listHeight = 0 on both #Preview and on the Simulator (running the iPad mini (6th generation) 18.1 simulation. More tomorrow -- hopefully with a sample project and an FB#.

I created a sample project demonstrating that .onScrollGeometryChange returns no data when applied to List, Form, or TextEdtior. FB19922481

Thank you for your help. I think this fixed it. Following your directions, Checked Xcode's Apple Accouts - Looked ok Set up a new project with a new AppID and CloudKit container. Worked. While in that new project, changed AppID and CloudKit container back to the problem values. FAILED. Logged in to Developer portal. No warnings or error messages and no pending agreements. Followed steps from TN3164. iCloud was checked. However, the option was "Compatible with Xcode 5". Changed it to "Include CloudKit support" and saved. Forced a reprovisioning by unchecking and rechecking the Automatic Signing feature in Xcode. WORKED. (I believe I said previously that this was an OLD app...) Thank you for your help. (I'll copy this into a reply in the FB to complete your records.)

This is a very nice addition to SwiftData, but there is still a problem (which I didn't mention in the original post). To the best of my knowledge, CloudKit still does not support (or enforce) unique properties. So, unless I'm missing something, this solution only works if you don't want take advantage of iCloud data synchronization services. Or am I missing something?

Your post is extremely interesting and definitely requires more thought on my part. It seems that what you're doing is to build a FocusCoordinator, conceptually similar to a Navigation Coordinator (although I think that there may be some missing APIs preventing a comprehensive solution. My immediate interest is on tab-navigation and I have some new information to offer about it. It turns out that in most cases, sending a <tab> to a focueed TextField will cause focus to change, BUT if the TextField is instantiated with the axis: AXIS parameter, the <tab> is added to the TextField body instead. I don't know how Apple will classify it, but I'm calling this a bug and have reported it. (FB20505919).