Skip to content

Conversation

@bryankeller
Copy link
Contributor

Details

This fixes some issues with calculating targetContentOffset, which specifically affected the bottomToTop layout used for message-like UIs.

In my next PR, I'm going to improve how we track state as batch updates and other invalidations occur. I have this working in a prototype layout, and the ideas should translate well to MagazineLayout.

Tested in example app and Airbnb app.

Types of changes

  • Docs change / refactoring / dependency upgrade
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

@bryankeller bryankeller added the bug Something isn't working label Oct 10, 2025
at: ElementLocation(indexPath: preferredAttributes.indexPath),
.afterUpdates).height
attributes.frame.origin.y -= (contentOffsetAdjustment?.y ?? 0)
.afterUpdates)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

much simpler - the math before was unnecessarily complex

@bryankeller bryankeller merged commit e211132 into master Oct 10, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants