introduce Fabric View Culling #49198

sammy-SC · 2025-02-05T11:37:10Z

Summary:
changelog: [internal]

The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy.

With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user.

Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance.

In the example bellow, view B will not be mounted because the user can't see it.
{F1974949953}

The difference in number of allocated views:
Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled removeClippedSubviews flag globally.
|Before|After:
| {F1974949979}| {F1974949981}

Disclaimer, this is not a complete implementation

This implementation is not complete and it is missing to handle edge cases.
Things that are missing:

Transform style is not taken into account.
removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view.
Fabric View Culling does not respect when ScrollView has overflow set to visible.
Fabric View Culling is only performant enough on iOS.
enableSynchronousStateUpdates must be enabled for Fabric View Culling to work correctly.

Differential Revision: D63458372

facebook-github-bot · 2025-02-05T11:37:30Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Differential Revision: D63458372

facebook-github-bot · 2025-02-05T13:35:13Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Differential Revision: D63458372

facebook-github-bot · 2025-02-05T16:26:36Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Differential Revision: D63458372

facebook-github-bot · 2025-02-05T16:36:49Z

This pull request was exported from Phabricator. Differential Revision: D63458372

facebook-github-bot · 2025-02-06T10:20:36Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: Pull Request resolved: facebook#49198 changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Differential Revision: D63458372

facebook-github-bot · 2025-02-06T11:06:11Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: Pull Request resolved: facebook#49198 changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Differential Revision: D63458372

facebook-github-bot · 2025-02-06T11:51:47Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Reviewed By: javache Differential Revision: D63458372

facebook-github-bot · 2025-02-06T17:57:31Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Reviewed By: javache Differential Revision: D63458372

facebook-github-bot · 2025-02-07T08:12:59Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Reviewed By: javache Differential Revision: D63458372

facebook-github-bot · 2025-02-07T11:34:35Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Reviewed By: javache Differential Revision: D63458372

facebook-github-bot · 2025-02-07T12:02:05Z

This pull request was exported from Phabricator. Differential Revision: D63458372

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Reviewed By: javache Differential Revision: D63458372

Summary: changelog: [internal] introduces feature flag for Fabric View Culling. Not used anywhere yet. Reviewed By: christophpurrer Differential Revision: D68775684

Summary: changelog: [internal] Adds new method to LayoutMetrics that calculates frame adjusted for overflow inset. For example, for the following view hierarchy. it would produce a frame that would fully contain view A and view B. ``` ┌─────────────┐ │<View A /> │ │ ┌───────┴─────┐ └─────┤<View B /> │ │ │ └─────────────┘ ``` See tests for more details Reviewed By: javache, lenaic Differential Revision: D68775683

Summary: changelog: [internal] The work done on the main thread should scale with what is on the screen. React Native shouldn’t block the main thread for off screen elements that do not affect what is shown to the end user. When React schedules a commit, only views needed to achieve a screen full of content should be materialised and added to the host platform’s view hierarchy. With Fabric View Culling, views that do not contribute pixels to the screen will not materialize and updates to them will be skipped. React Native will focus system resources on what is visible to the end user. Fabric View Culling maximises benefits from view recycling. Each UI element such as text, image, or video is recycled individually. As soon as an item goes off screen, it can be reused anywhere in the UI and pieced together with other items to create new UI elements. Such recycling reduces the need of having multiple view types and improves memory usage and scroll performance. In the example bellow, view B will not be mounted because the user can't see it. {F1974949953} The difference in number of allocated views: Please note, the screenshots below are from Xcode View Hierarchy debugger. To show how many views are allocated in memory, I disabled [removeClippedSubviews](https://reactnative.dev/docs/scrollview#removeclippedsubviews) flag globally. |Before|After: | {F1974949979}| {F1974949981} # Disclaimer, this is not a complete implementation This implementation is not complete and it is missing to handle edge cases. Things that are missing: - Transform style is not taken into account. - removeClippedSubviews is not respected. Fabric View Culling happens unconditionally for every scroll view. - Fabric View Culling does not respect when ScrollView has overflow set to visible. - Fabric View Culling is only performant enough on iOS. - [enableSynchronousStateUpdates](https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js#L248) must be enabled for Fabric View Culling to work correctly. Reviewed By: javache Differential Revision: D63458372

facebook-github-bot · 2025-02-07T15:46:31Z

This pull request was exported from Phabricator. Differential Revision: D63458372

facebook-github-bot · 2025-02-07T17:41:54Z

This pull request has been merged in 947d9c3.

facebook-github-bot added CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. p: Facebook Partner: Facebook Partner labels Feb 5, 2025

facebook-github-bot added the fb-exported label Feb 5, 2025

sammy-SC force-pushed the export-D63458372 branch from 77a04bb to 566d766 Compare February 5, 2025 13:35

sammy-SC force-pushed the export-D63458372 branch from 566d766 to 478abe6 Compare February 5, 2025 16:26

sammy-SC force-pushed the export-D63458372 branch from 478abe6 to 5d88571 Compare February 5, 2025 16:36

sammy-SC force-pushed the export-D63458372 branch from 5d88571 to 1a950c0 Compare February 6, 2025 10:20

sammy-SC force-pushed the export-D63458372 branch from 1a950c0 to e85e6d4 Compare February 6, 2025 11:06

sammy-SC force-pushed the export-D63458372 branch from e85e6d4 to 7c3f552 Compare February 6, 2025 11:51

sammy-SC force-pushed the export-D63458372 branch from 7c3f552 to 7d8e79c Compare February 6, 2025 17:57

sammy-SC force-pushed the export-D63458372 branch from 7d8e79c to 6bf45c9 Compare February 7, 2025 08:12

sammy-SC force-pushed the export-D63458372 branch from 6bf45c9 to d9cd99f Compare February 7, 2025 11:34

sammy-SC force-pushed the export-D63458372 branch from d9cd99f to 798a998 Compare February 7, 2025 12:01

sammy-SC added 3 commits February 7, 2025 07:45

introduce feature flag for View Culling (facebook#49196)

ec5bd77

Summary: changelog: [internal] introduces feature flag for Fabric View Culling. Not used anywhere yet. Reviewed By: christophpurrer Differential Revision: D68775684

sammy-SC force-pushed the export-D63458372 branch from 798a998 to d7c9b31 Compare February 7, 2025 15:46

facebook-github-bot closed this in 947d9c3 Feb 7, 2025

facebook-github-bot added the Merged This PR has been merged. label Feb 7, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

introduce Fabric View Culling #49198

introduce Fabric View Culling #49198

sammy-SC commented Feb 5, 2025

facebook-github-bot commented Feb 5, 2025

facebook-github-bot commented Feb 5, 2025

facebook-github-bot commented Feb 5, 2025

facebook-github-bot commented Feb 5, 2025

facebook-github-bot commented Feb 6, 2025

facebook-github-bot commented Feb 6, 2025

facebook-github-bot commented Feb 6, 2025

facebook-github-bot commented Feb 6, 2025

facebook-github-bot commented Feb 7, 2025

facebook-github-bot commented Feb 7, 2025

facebook-github-bot commented Feb 7, 2025

facebook-github-bot commented Feb 7, 2025

facebook-github-bot commented Feb 7, 2025

introduce Fabric View Culling #49198

introduce Fabric View Culling #49198

Conversation

sammy-SC commented Feb 5, 2025

Disclaimer, this is not a complete implementation

facebook-github-bot commented Feb 5, 2025

facebook-github-bot commented Feb 5, 2025

facebook-github-bot commented Feb 5, 2025

facebook-github-bot commented Feb 5, 2025

facebook-github-bot commented Feb 6, 2025

facebook-github-bot commented Feb 6, 2025

facebook-github-bot commented Feb 6, 2025

facebook-github-bot commented Feb 6, 2025

facebook-github-bot commented Feb 7, 2025

facebook-github-bot commented Feb 7, 2025

facebook-github-bot commented Feb 7, 2025

facebook-github-bot commented Feb 7, 2025

facebook-github-bot commented Feb 7, 2025