lexical

Description Instead of sending value 0 as a static value we take the current format from selection.format and pass it to the respective function responsible for format change. As a result the format gets passed on between multiple linebreaks. Closes #8160 Before After

Description This PR fixes an issue where SVGs inserted without explicit and attributes (such as dimensionless SVGs or base64 data URIs) would visually collapse to in the editor. The Problem When a dimensionless SVG or a base64 SVG string is parsed: 1. The browser reports and as . 2. The constructor defaults missing dimensions to . 3. In the React layer (), the previous fallback logic relied on a fragile check that failed for base64 data URIs. 4. Because the intrinsic dimensions were , the component rendered with inline styles, making the node invisible and unselectable. The Fix I pivoted from a global fallback to a Surgical SVG Fallback to maintain compatibility with Lexical's existing E2E test suite: Updated the logic to identify SVGs using both file extensions and prefixes. Preserved CSS Inheritance: Standard images (JPG/PNG) continue to return for dimensions. This ensures that existing E2E tests (which rely on specific HTML snapshots for standard images) remain green and global CSS remains in control of responsive sizing. SVG Math Safety Net: For SVGs specifically, if no intrinsic dimensions are found, the logic now falls back to the node's . This ensures a visible bounding box is rendered, allowing the user to see, select, and resize the image. Fixes #7511 Test Plan New Test: Added -> "Dimensionless SVG renders with a visible bounding box instead of collapsing". This verifies that a base64 encoded SVG without attributes renders with a width/height > 0. Regressions: Verified that standard image snapshots (e.g., the "Yellow Flower" JPG in ) still receive to satisfy existing Playwright assertions. Local Verification:** Ran and confirmed all 600+ tests pass.

Leading and trailing whitespaces inside formatted text are already moved outside the formatted region to ensure correct markdown. But if the formatted text only contain whitespace, then we end up with formatting for the empty string, e.g. for a bold whitespace. So we need to skip the formatting in these cases. The previous attempt at fixing this in #7400 used html entities to escape leading/trailing whitespaces inside formatted texts, but this breaks commonmark. Example that breaks when using html entities: https://spec.commonmark.org/dingus/?text=bold%20space%20with%20adjacent%20text%3A%20%26%2332%3Badjacent%0A%0A Reverts #7400 Closes #7575 Test plan Automated test in Before After