Skip to content

Commit 1ecff77

Browse files
rubennortemeta-codesync[bot]
authored andcommitted
Document why EventTarget feature flags stay at ossReleaseStage 'none' (#57527)
Summary: Pull Request resolved: #57527 Add TODO comments to the `enableImperativeEvents` and `enableNativeEventTargetEventDispatching` feature flags explaining why they haven't progressed yet (the OSS renderer cannot be upgraded with the necessary changes until React 19.3.0 is released). This is a comment-only change with no functional impact. Changelog: [Internal] Reviewed By: huntie Differential Revision: D111695477 fbshipit-source-id: e124ed4a032cb0a7a05eeb5ae83832b1eb0b1622
1 parent 96d3f91 commit 1ecff77

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

packages/react-native/scripts/featureflags/ReactNativeFeatureFlags.config.js

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1033,8 +1033,10 @@ const definitions: FeatureFlagDefinitions = {
10331033
expectedReleaseValue: true,
10341034
purpose: 'release',
10351035
},
1036+
// TODO: This should be "canary" now but the OSS renderer cannot be upgraded with the necessary changes until React 19.3.0 is released.
10361037
ossReleaseStage: 'none',
10371038
},
1039+
// TODO: This feature flag should be shipped and clean up now, but the OSS renderer cannot be upgraded with the necessary changes until React 19.3.0 is released.
10381040
enableNativeEventTargetEventDispatching: {
10391041
defaultValue: false,
10401042
metadata: {

0 commit comments

Comments
 (0)