react / react/react-native

measurement y values for nodes used in stickyHeaderIndices do not match it's sticky positioning

Open
#51,911 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs: Triage :mag: Type: New Architecture
Dominant language
C++
Stars
127k
Forks
25.3k
Avg merge
1d 23h
Merged PRs (30d)
4

Description

Description

When a node which is included in a list that specifies it in it's stickyHeaderIndices is measured via it's ref using measure or measureInWindow, the y and pageY values reflect the node's original coordinates and do not account for it's sticky positioning.

Steps to reproduce
  1. Scroll a list until the node(s) in stickyHeaderIndices become sticky
  2. Measure the sticky node via it's ref

Expected:

Coordinates reflect it's current, sticky position on the screen or in the viewport, like how it works on the legacy architecture.

Actual:

Coordinates reflect it's original positioning, not accounting for it's sticky position, so once the element becomes sticky due to scroll the y values will be negative.

React Native Version

0.79.2

Affected Platforms

Runtime - iOS

Areas

Other (please specify), Fabric - The New Renderer

Output of npx @react-native-community/cli info
System:
  OS: macOS 14.6.1
  CPU: (12) arm64 Apple M2 Pro
  Memory: 154.50 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.19.1
    path: /usr/local/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.yarn/bin/yarn
  npm:
    version: 10.8.2
    path: /usr/local/bin/npm
  Watchman:
    version: 2024.09.09.00
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.11.3
    path: /Users/adamhari/.rvm/gems/ruby-2.7.6/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.2
      - iOS 18.2
      - macOS 15.2
      - tvOS 18.2
      - visionOS 2.2
      - watchOS 11.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11330709
  Xcode:
    version: 16.2/16C5032a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 2.7.6
    path: /Users/adamhari/.rvm/rubies/ruby-2.7.6/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 19.0.0
    wanted: 19.0.0
  react-native:
    installed: 0.79.2
    wanted: 0.79.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
Stacktrace or Logs
n/a
MANDATORY Reproducer

https://snack.expo.dev/@adamhari-kashoo/measure-y-value-incorrect-for-element-in-stickyheaderindices

Screenshots and Videos

https://github.com/user-attachments/assets/cec10b97-ac2e-4931-b920-0fe045725f38

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the mandatory Snack reproducer on iOS and comparing measurements before and after a node in stickyHeaderIndices becomes sticky. Investigate the Fabric measurement behavior for measure and measureInWindow, using the legacy architecture's result as the expected reference. Done means the reported y and pageY coordinates reflect the node's current sticky position rather than its original position.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, react-native
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.