Disable moveBefore experiment (#33348)
There seems to be some bugs still to work out in Chrome. See #33187. Additionally, since you can't really rely on this function existing across browsers, it's hard to depend on its behavior anyway. In fact, you now have a source of inconsistent behaviors across browsers to deal with. Ideally it would also be more widely spread in fake DOM implementations like JSDOM so that we can use it unconditionally. #33177. We still want to enable this since it's a great feature but maybe not until it's more widely available cross-browsers with fewer bugs.
Sebastian Markbåge committed
May 23, 2025 at 13:25 UTC
6a1dfe37776e5a41f4c1e07c33cf1f26c4a82979
1 file changed
+1
-1
packages/shared/ReactFeatureFlags.js
+1
-1
@@ -194,7 +194,7 @@ export const disableLegacyContext = true;
194
export const disableLegacyContextForFunctionComponents = true;
195
196
// Enable the moveBefore() alternative to insertBefore(). This preserves states of moves.
197
-export const enableMoveBefore = __EXPERIMENTAL__;
197
+export const enableMoveBefore = false;
198
199
// Disabled caching behavior of `react/cache` in client runtimes.
200
export const disableClientCache = true;