Skip to content

Stop sending unused "scroll" key in View props diff (#59680) - #59680

Open
coado wants to merge 4 commits into
react:mainfrom
coado:export-D128598698
Open

coado wants to merge 4 commits into
react:mainfrom
coado:export-D128598698

Conversation

@coado

@coado coado commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Summary:

HostPlatformViewProps::getDiffProps sends a scroll key with the same value as overflow whenever clipping changes. No Android view manager has a scroll prop and nothing reads that key directly; every component reads overflow. ViewProps.SCROLL is the overflow value "scroll", not a prop name. The key only adds a JNI string and a failed setter lookup per update, so remove it.

Changelog:
[Internal]

Differential Revision: D128598698

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 30, 2026
@facebook-github-tools facebook-github-tools Bot added p: Software Mansion Partner: Software Mansion Partner p: Facebook Partner: Facebook labels Oct 30, 2026
@meta-codesync

meta-codesync Bot commented Oct 30, 2026

Copy link
Copy Markdown

@coado has exported this pull request. If you are a Meta employee, you can view the originating Diff in D128598698.

coado added 4 commits November 5, 2026 11:26
Summary:
Props diffing (`enablePropsUpdateReconciliationAndroid`) applies to every component whose props implement `getDiffProps`, which includes all codegen components. On view creation, props equal to their C++ default are not sent, so a native component whose default differs from the C++ default ends up with the wrong value. Third-party components have not been checked for this, which makes the existing flag unsafe to try in OSS.

This adds `enableCoreComponentsPropsUpdateReconciliationAndroid`, released in the experimental stage, which enables props diffing only for the core components with hand-written props (View, Paragraph, Text, RawText, TextEffect, Image, ScrollView). All other components keep receiving raw props.

TextInput is intentionally not included: on Android its component name is `AndroidTextInput` while its props report `TextInput` as the diffing target, so props diffing has never applied to it under either flag. Fixing that is left for a separate change.

The decision now lives in a single non-virtual function, `isPropsDiffingEnabled`, used by both `FabricMountingManager::getProps` and `ConcreteComponentDescriptor::cloneProps`, so the two decisions cannot diverge. Behavior with the new flag off is unchanged.

The Android ScrollViews (vertical, nested and horizontal) switch their native default `overflow` from `scroll` to `visible` under props diffing, because the C++ default `visible` is never sent. This switch only checked `enablePropsUpdateReconciliationAndroid`, so with only the new flag enabled ScrollViews clipped their content. The default is now resolved in one place, `ReactScrollViewHelper.getDefaultOverflow()`, which checks both flags.

Changelog:
[Android][Added] - Add experimental feature flag `enableCoreComponentsPropsUpdateReconciliationAndroid` to send prop updates based on props diffing for core components only

Differential Revision: D127587361
Summary:
This diff enables props diffing for the TextInput component on Android.

Changelog:
[Android][Fixed] - Fix props diffing never being applied to `TextInput` when props update reconciliation is enabled

Differential Revision: D128563541
Summary:
Pull Request resolved: react#59679

For some props, their C++ defaults did not equal platform defaults. With props diffing enabled, default value is not sent, so the platform one is assumed. Some defaults did not match:

- `showSoftInputOnFocus` and `allowFontScaling` defaulted to `false` in C++ but are `true` natively, so setting them to `false` from JS had no effect.
- `autoCorrect` was a plain `bool` defaulting to `false`, while the native setter has three states (on, off, unset). `autoCorrect={false}` was never sent and removing the prop could not restore the platform default. It is now `std::optional<bool>` and is sent as `null` when unset.
- `numberOfLines`, `textBreakStrategy` and `includeFontPadding` were each emitted twice, once from the paragraph attributes and once from a duplicate flat field, with the later one overwriting the earlier. The flat `includeFontPadding` defaulted to `false` while the native default is `true`, so removing `includeFontPadding={true}` sent `false`. These keys are now only emitted from the paragraph attributes.

Changelog:
[Android][Fixed] - Fix `TextInput` props `showSoftInputOnFocus`, `allowFontScaling`, `autoCorrect` and `includeFontPadding` being ignored or reset incorrectly when props diffing is enabled

Differential Revision: D128594780
Summary:
Pull Request resolved: react#59680

`HostPlatformViewProps::getDiffProps` sends a `scroll` key with the same value as `overflow` whenever clipping changes. No Android view manager has a `scroll` prop and nothing reads that key directly; every component reads `overflow`. `ViewProps.SCROLL` is the overflow value `"scroll"`, not a prop name. The key only adds a JNI string and a failed setter lookup per update, so remove it.

Changelog:
[Internal]

Differential Revision: D128598698
@meta-codesync meta-codesync Bot changed the title Stop sending unused "scroll" key in View props diff Stop sending unused "scroll" key in View props diff (#59680) Nov 5, 2026
@coado
coado force-pushed the export-D128598698 branch from c13b714 to b2a032d Compare November 5, 2026 19:28

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported p: Facebook Partner: Facebook p: Software Mansion Partner: Software Mansion Partner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant