Nick Gerleman

This commit **removes** the `fixTextClippingAndroid15useBoundsForWidth` feature flag and all associated code, effectively **reverting** the **Android text layout measurement** logic to its stable, advance-based method. This **maintenance** and **bug fix** addresses multiple reported text clipping issues by eliminating a problematic visual-bounds-based width calculation in `TextLayoutManager.kt` that was never shipped. The deletion encompasses the entire feature flag plumbing across C++, JNI, Kotlin, and JavaScript, ensuring a more reliable and consistent **text rendering** experience on **Android** by removing an unstable, experimental path.

This commit provides a **bug fix** for a **crash** occurring in the **React Native Android text measurement system** when `FabricUIManager.prepareTextLayout()` attempts to measure text for a surface that has already been stopped. The issue stemmed from `surfaceMountingManager.getContext()` returning `null`, which was then used to retrieve the `AssetManager` for font resolution. The **core change** involves **refactoring** text layout and measurement functions across `FabricUIManager.java`, `TextLayoutManager.kt`, `FontMetricsUtil.kt`, `ReactTextViewManager.kt`, and `ReactTextInputManager.kt` to directly accept the application's `AssetManager`. This **eliminates the crash** by bypassing the problematic context lookup, ensuring consistent font resolution, and clarifying that text layout is independent of activity-specific contexts.

This commit provides a **bug fix** for the **Android text rendering** system, specifically within `TextLayoutManager.kt`. It resolves a crash that occurred when `BoringLayout.isBoring()` would sometimes return text metrics with a negative width for certain strings, even on Android 15+. The fix introduces a check within the `isBoring` function to detect these invalid negative widths, and when found, it **falls back to using `StaticLayout`** for layout calculation. This prevents application crashes and significantly improves the **stability of text layout** for edge-case strings on Android.

This commit **enhances the readability of debug output** by standardizing the representation of floating-point `NaN` and `Infinity` values. It modifies the `toString` function within the **`DebugStringConvertible`** utility in `ReactCommon/react/renderer/debug` to render these as "NaN", "Infinity", and "-Infinity" instead of their lowercase stream defaults. This **maintenance** change **aligns React Native debug strings with developer expectations and JavaScript conventions**, making logs and snapshots clearer. Snapshot tests for **`Pressable`** and **`Text`** components were updated to reflect this improved rendering.

This commit provides a **build fix** for the **Yoga layout engine** within **React Native**, specifically addressing a **GCC `-Werror=return-type` warning**. It modifies `packages/react-native/ReactCommon/yoga/yoga/YGNodeStyle.cpp` by adding `fatalWithMessage` calls to the `gridTrackSizeFromTypeAndValue` and `styleSizeLengthFromTypeAndValue` functions. This ensures that exhaustive switch statements in these functions explicitly handle all code paths, preventing compilation failures when building with GCC's strict warning flags. The change improves **compiler compatibility** and maintains the robustness of the styling and layout calculation logic.

This commit **fixes flaky test comparisons** in **Fantom test assertions** by standardizing the **debug output of float values** to 4 decimal places. It **refactors** the `toString` method in `DebugStringConvertible.cpp` to use `snprintf` for this formatting, replacing the `double-conversion` library and removing its dependency from the build system. This ensures consistent debug layout metrics across platforms, impacting numerous `itest.js` files that have been updated to reflect the new output. Since this change is confined to debug-only code, the precision adjustment is safe for all consumers and improves overall test reliability.

This commit **significantly expands the E2E testing coverage** for the **`Text` component** by introducing **screenshot tests** for nine visual examples that previously lacked automated validation. These new tests target specific `Text` properties and behaviors such as `wrap`, `padding`, `fontVariants`, and `lineHeightIOS`, ensuring their correct rendering on both **iOS and Android platforms**. The **maintenance work** involved adding `name` and `testID` attributes to the respective examples in `TextExample.ios.js` and `TextExample.android.js`. This effort improves the **reliability and visual regression detection** for these critical UI elements, bolstering the overall stability of the **`Text` component's visual presentation** across platforms.

This commit **adds new E2E screenshot tests** for the **Transform component examples**, significantly enhancing test coverage and stability. It introduces `name` fields and `testID` props to 10 static examples within `TransformExample.js`, then creates corresponding E2E tests to capture their visual output. This **new capability** improves the **reliability** of the `Transform` component by ensuring visual consistency, while intentionally skipping animated examples to avoid non-deterministic test results.

This commit **adds end-to-end (E2E) tests** for the `Alert` component, significantly improving its test coverage. It **modifies `AlertExample.js`** by adding `name` fields to two existing `Alert` examples, which enables the creation of two corresponding E2E interaction tests. These **new E2E tests** specifically verify that the trigger buttons for both default-button and three-button `Alert` variants are visible and clickable, focusing on the interaction rather than the native dialog itself due to screenshot limitations. This **new testing capability** enhances the **reliability** of the `Alert` component by ensuring its core interaction mechanisms function correctly.

This commit **introduces new E2E screenshot tests** for the **`Button` component**, significantly enhancing **UI regression prevention** for its visual rendering. It updates five `Button` examples in `ButtonExample.js` by adding `name` fields, which are then used to create corresponding screenshot tests. These tests cover critical `Button` states, including default styling, custom colors, flexbox layouts for multiple buttons, and disabled variants, ensuring visual consistency across these common configurations.

This commit **enhances the E2E testing suite** by introducing new tests for three `Filter` component examples within **RNTester**: `blur-with-overflow`, `drop-shadow`, and `animated-blur`. It adds **screenshot tests** for `blur-with-overflow` and `drop-shadow` to visually validate their rendering. For `animated-blur`, an **interaction test** was implemented to verify its dynamic behavior, which required adding `testID` props to relevant UI elements in `AnimatedBlurExample`. This **maintenance work** significantly improves the **test coverage** and stability of these visual effects, helping to prevent future regressions.

This commit **adds End-to-End (E2E) screenshot tests** for ten visual examples of the **`Text` component**, significantly improving test coverage for its styling properties. New E2E test files were introduced to validate properties such as `fontFamily`, `fontWeight`, `fontSize`, and `color`, ensuring their visual consistency across platforms. To enable these tests, `name` and `testID` attributes were added to corresponding examples in `TextExample.ios.js` and `TextExample.android.js`. This **enhances the quality assurance** for the core `Text` component, helping to prevent visual regressions in its rendering.

This commit introduces **new E2E screenshot tests** for the **legacy `BoxShadow` component** within the RNTester app. It enhances `BoxShadowExample.js` by adding `name` fields and `testID` props to five cross-platform examples, enabling automated visual regression testing. These tests specifically target **iOS platforms** to ensure the visual fidelity and stability of `BoxShadow` rendering, as the component is currently only registered for iOS in the `RNTesterList`. This work significantly improves the **test coverage** for a core UI component, excluding Android and Mac platforms where `BoxShadow` is not registered or elevation examples are not relevant.

This commit introduces **new E2E tests** for the **`Pressable` component**, significantly enhancing its test coverage and reliability. It modifies `PressableExample.js` by adding `name` fields to four existing `Pressable` examples to enable targeted testing. The new tests specifically cover critical interaction scenarios such as `content-press`, `feedback-events`, `text-press`, and `hit-slop`, verifying correct click behavior and text state changes. This **enhances the quality assurance** for the `Pressable` component by ensuring its core interactions function as expected across various user input scenarios.

This commit **adds new E2E tests** for the **`Text` component** within RNTester, specifically targeting two previously uncovered examples. It introduces a screenshot test to verify the rendering of `boxShadow` and an interaction test for `textWithLinkRole` that captures visual state changes when a link is pressed. This work represents a **new capability** that significantly enhances the **test coverage** and reliability for critical styling and interactive features of the `Text` component, ensuring their correct behavior.

This commit **enhances the testing suite** for **React Native's `Touchable` components** by introducing **new End-to-End (E2E) interaction tests**. It adds `name` fields to four existing `Touchable` examples within `TouchableExample.js` to facilitate testing. The new tests specifically cover `highlight`, `without-feedback`, `feedback-events`, and `hit-slop` behaviors, verifying correct click interactions and text state changes. This work significantly **improves the reliability and stability** of `Touchable` components by ensuring their core functionalities behave as expected across various interaction scenarios.

This commit introduces **new end-to-end (E2E) screenshot tests** for the **Filter** component's static visual examples within the **RNTester** application. Specifically, it adds visual regression tests for seven filter types, including `opacity`, `contrast`, `grayscale`, `saturate`, `hueRotate`, and platform-specific `sepia` and `invert` filters on Android. By modifying `FilterExample.js` to include `testID` props and creating dedicated E2E test files, this work significantly **enhances the testing coverage** and helps ensure the **visual consistency and correctness** of these filter effects across different environments. This **testing improvement** is crucial for preventing visual regressions in the `Filter` component.

This commit **expands the E2E testing suite** by introducing **screenshot tests for seven visual examples of the `Image` component**, significantly improving coverage for its rendering behavior. It adds new tests for `static-image`, `tint-color`, `opacity`, `nesting-content`, `nesting-image-background`, `blur-radius`, and `base64-image` within `ImageExample.js`, which previously lacked dedicated E2E validation. This **new capability** ensures greater **visual consistency and reliability** for the `Image` component across platforms, with most tests being cross-platform and `base64-image` being iOS-specific.

This commit **enhances the E2E testing suite** by introducing **new screenshot tests** for the **`ActivityIndicator` component** and the **`Appearance` API**. It achieves this by adding `name` fields to existing examples for both `ActivityIndicator` (covering default and custom-color variants) and `Appearance` (testing forced-light and forced-dark themes). These **new E2E tests** significantly **improve visual regression testing** for these fundamental UI elements and theme management, helping to catch unintended visual changes and ensuring greater stability for core UI components.

This commit performs a significant **refactoring** of the **Yoga JavaScript bindings** by entirely removing the `embind` layer, which previously bridged C++ wrapper classes to JavaScript. JavaScript now directly calls Yoga's C API through a thin C bridge (`wasm_bridge.c`) and rewritten JS classes (`wrapAssembly.ts`), which manage WASM pointers and tree hierarchy. This change **optimizes performance** and **reduces bundle size** by eliminating `embind`'s overhead, resulting in up to 4.3x faster layout calculations and a 16.2% smaller gzipped bundle. The public API shape for `Yoga`, `Node`, and `Config` types remains **identical**, ensuring no breaking changes for consumers while delivering substantial improvements.