feat: add support for transforming vw and vh units into calc() expressions using CSS variables.

[PupilTong]

Summary by CodeRabbit

• New Features

  • rpx unit support: inline rpx values transform to calc(...) using configurable --rpx-unit
  • New transform-vw / transform-vh attributes/properties to optionally transform vw/vh → calc(...) via --vw-unit / --vh-unit

• Style

  • Added container-query defaults and CSS custom properties (--rpx-unit, --vw-unit, --vh-unit) with @Property registrations

• Tests

  • Added e2e and unit tests for rpx and vw/vh behaviors

• Breaking Changes

  • rpx support marked as breaking in the changeset

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).
• Changeset added, and when a BREAKING CHANGE occurs, it needs to be clearly marked (or not required).

[changeset-bot]

🦋 Changeset detected

Latest commit: e0de618

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages

Name	Type
@lynx-js/web-core	Minor
upgrade-rspeedy	Patch
@lynx-js/web-rsbuild-server-middleware	Minor
@lynx-js/template-webpack-plugin	Patch
@lynx-js/react-rsbuild-plugin	Patch
create-rspeedy	Patch
@lynx-js/web-worker-rpc	Minor
@lynx-js/react-alias-rsbuild-plugin	Patch
@lynx-js/rspeedy	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds configurable viewport-unit transformations (rpx, vw, vh) across CSS defaults, Rust style-transformer, WASM bindings, and TypeScript worker/main-thread paths; tests and E2E cover the new behavior. Changes introduce TransformerConfig and thread transform flags through encode/decode and inline-style APIs.

Changes

Cohort / File(s)	Summary
Changesets \.changeset/transform-rpx.md, \.changeset/transform-vw-vh-support.md	Added changesets announcing rpx and vw/vh transform support (rpx marked breaking).
CSS Base packages/web-platform/web-core/css/index.css	Added container query defaults, --rpx-unit/--vw-unit/--vh-unit defaults and @property registrations.
Rust: Transformer Core packages/web-platform/web-core/src/style_transformer/token_transformer.rs, .../transformer.rs, .../inline_style.rs, .../mod.rs	Introduced TransformerConfig (transform_vw/transform_vh), threaded config through StyleTransformer, added conditional vw/vh → calc(...) transforms, and made token_transformer public.
Rust: Main Thread & Server packages/web-platform/web-core/src/main_thread/client/element_apis/style_apis.rs, .../server/main_thread_server_context.rs	Extended inline-style APIs and MainThreadServerContext to accept transform flags and pass them into transformation pipeline.
Rust: Style Info / Decoder packages/web-platform/web-core/src/template/.../decoded_style_data.rs, .../style_info_decoder.rs, .../raw_style_info.rs	Extended WASM-exposed encode/decode and StyleInfoDecoder to accept and forward transform_vw/transform_vh flags.
WASM / .d.ts Bindings packages/web-platform/web-core/binary/*/client*.d.ts, .../*_bg.wasm.d.ts, .../encode/*.d.ts, .../server/*.d.ts, .../client_legacy/*	Updated TypeScript/WASM declaration signatures to include two extra boolean parameters for style encode/decode and inline-style functions; adjusted wasm arities.
TypeScript: Worker & Loader packages/web-platform/web-core/ts/client/decodeWorker/decode.worker.ts, .../cssLoader.ts, .../types.ts	Threaded transformVW/transformVH through worker message types and style loading (JSON and wasm) paths.
TypeScript: Main Thread & TemplateManager packages/web-platform/web-core/ts/client/mainthread/LynxView.ts, .../LynxViewInstance.ts, .../TemplateManager.ts	Added observed transform-vw/transform-vh attributes/properties and passed flags into instance/template fetch flows.
TypeScript: Element API Creation packages/web-platform/web-core/ts/client/mainthread/elementAPIs/createElementAPI.ts, packages/web-platform/web-core/ts/server/elementAPIs/createElementAPI.ts	createElementAPI accepts transform flags and forwards them to inline-style setters and server MainThreadServerContext.
TypeScript: Server APIs packages/web-platform/web-core/ts/server/decode.ts, packages/web-platform/web-core/ts/server/deploy.ts	decodeTemplate and executeTemplate gain transformVW/transformVH and forward them into decoding/deploy flows.
Tests & E2E packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts, .../basic-rpx-unit/index.jsx, .../basic-vw-vh-unit/index.jsx, packages/web-platform/web-core/tests/**, .../template-manager.spec.ts	Added unit and E2E tests for rpx/vw/vh behavior; updated test call sites to new signatures.
Misc / Dev Middleware packages/web-platform/web-core-e2e/shell-project/devMiddleware.ts	Forwarded transform flags into executeTemplate in dev middleware.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Possibly related PRs

• feat: improve web-core-wasm #2148: Alters the same style encode/decode bindings and inline-style APIs that now accept transform flags.
• feat: Add web-core-wasm package #2039: Overlaps with changes to the style_transformer/token_transformer pipeline and unit conversions.
• perf(web): rewrite style transformer in rust #1094: Touches the Rust style-transformer/tokenization code extended here.

Suggested reviewers

• Sherry-hue

Poem

🐰 I hopped through tokens, thin and spry,
rpx, vw, and vh learn to fly,
From Rust to WASM, calc lines hum,
Units dance bright where styles come from,
🥕✨ — a rabbit cheers the new sky

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 67.53% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main feature added in this PR: support for transforming vw and vh units into calc() expressions using CSS variables.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

❌ Patch coverage is 61.53846% with 135 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...platform/web-core/ts/client/mainthread/LynxView.ts	0.00%	43 Missing ⚠️
.../src/main_thread/client/element_apis/style_apis.rs	0.00%	24 Missing ⚠️
...template_sections/style_info/decoded_style_data.rs	0.00%	20 Missing ⚠️
...c/main_thread/server/main_thread_server_context.rs	34.48%	19 Missing ⚠️
.../web-core/ts/client/mainthread/LynxViewInstance.ts	0.00%	13 Missing ⚠️
...orm/web-core/src/style_transformer/inline_style.rs	74.41%	11 Missing ⚠️
...template_sections/style_info/style_info_decoder.rs	78.94%	4 Missing ⚠️
...ate/template_sections/style_info/raw_style_info.rs	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[codspeed-hq]

Merging this PR will not alter performance

✅ 63 untouched benchmarks
⏩ 21 skipped benchmarks¹

---

_{Comparing PupilTong:p/hw/support-rpx-and-vw-vh (e0de618) with main (36b38eb)}

Footnotes

1. 21 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[relativeci]

Web Explorer

#8419 Bundle Size — 727.67KiB (+0.41%).

e0de618(current) vs 36b38eb main#8397(baseline)

Bundle metrics   5 changes 2 regressions

	Current #8419	Baseline #8397
Initial JS	42.62KiB(+1.49%)	41.99KiB
Initial CSS	2.13KiB(+6.97%)	1.99KiB
Cache Invalidation	49.08%	0%
Chunks	8	8
Assets	10	10
Modules	150(+0.67%)	149
Duplicate Modules	11	11
Duplicate Code	34.73%(-0.06%)	34.75%
Packages	3	3
Duplicate Packages	0	0

Bundle size by type   3 changes 3 regressions

	Current #8419	Baseline #8397
Other	384.29KiB (+0.5%)	382.38KiB
JS	341.25KiB (+0.26%)	340.36KiB
CSS	2.13KiB (+6.97%)	1.99KiB

Bundle analysis report Branch PupilTong:p/hw/support-rpx-and-v... Project dashboard

---

^{Generated by RelativeCI Documentation Report issue}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)

packages/web-platform/web-core/tests/element-apis.spec.ts (3)

1375-1391: ⚠️ Potential issue | 🟡 Minor

Missing transformVW and transformVH in SSR test config.

The createServerElementAPI config object is missing the newly required transformVW and transformVH properties. Based on the changes to packages/web-platform/web-core/ts/server/elementAPIs/createElementAPI.ts (lines 99-100), these are now required fields in the config type.

🔧 Proposed fix

       const config = {
         enableCSSSelector: true,
         defaultOverflowVisible: false,
         defaultDisplayLinear: true,
+        transformVW: false,
+        transformVH: false,
       };

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/web-platform/web-core/tests/element-apis.spec.ts` around lines 1375
- 1391, The test's config passed to createServerElementAPI is missing the
now-required numeric callbacks transformVW and transformVH; update the config
object used in the 'create element infer css id from parent component in SSR'
test to include transformVW and transformVH properties (functions returning
numbers) so the config shape matches the new createElementAPI expectations and
the call to createServerElementAPI compiles.

---

1461-1465: ⚠️ Potential issue | 🟡 Minor

Missing transform_vw and transform_vh parameters in decode_style_info call.

The decode_style_info function signature was updated to require two additional boolean parameters (transform_vw, transform_vh), but this call site was not updated.

🔧 Proposed fix

     const encodedStyleInfo = wasmInstance.decode_style_info(
       encodedRawStyleInfo,
       undefined,
       true,
+      false,
+      false,
     );

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/web-platform/web-core/tests/element-apis.spec.ts` around lines 1461
- 1465, Call to wasmInstance.decode_style_info is missing the two new boolean
parameters transform_vw and transform_vh; update the invocation (the
encodedStyleInfo assignment) to include those two booleans (e.g., pass false,
false or the appropriate test variables) so the call matches the updated
signature: decode_style_info(encodedRawStyleInfo, undefined, true, transform_vw,
transform_vh).

---

1413-1428: ⚠️ Potential issue | 🟡 Minor

Missing transformVW and transformVH in second SSR test config.

Same issue as the previous SSR test - the config object needs the new required properties.

🔧 Proposed fix

       const config = {
         enableCSSSelector: true,
         defaultOverflowVisible: false,
         defaultDisplayLinear: true,
+        transformVW: false,
+        transformVH: false,
       };

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/web-platform/web-core/tests/element-apis.spec.ts` around lines 1413
- 1428, The test "create element wont infer css id if parent css id is 0 in SSR"
passes a config to createServerElementAPI but omits the required transformVW and
transformVH properties; add transformVW and transformVH to the config object
used in this test (the same properties used in the previous SSR test) so the
config matches the expected shape when calling createServerElementAPI.

🧹 Nitpick comments (2)

packages/web-platform/web-core/src/style_transformer/mod.rs (1)

18-18: Narrow visibility unless external consumers are intentionally supported.

Line 18 makes token_transformer part of the public crate API. Based on current usage, this appears to be internal-only and can be crate-scoped to avoid unnecessary long-term API surface.

Proposed change

- pub mod token_transformer;
+ pub(crate) mod token_transformer;
+ pub(crate) use token_transformer::TransformerConfig;

Based on learnings: CSS processing in packages/web-platform/web-core/src/{css_tokenizer,style_transformer}/**/*.rs should stay focused and efficient; keeping API surface minimal helps maintain that boundary.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/web-platform/web-core/src/style_transformer/mod.rs` at line 18, The
module declaration `pub mod token_transformer` unnecessarily exposes internal
APIs; change it to a crate-private module by replacing the `pub mod
token_transformer` declaration with a private `mod token_transformer`, then
update any external references that relied on the public path (or add a minimal,
intentional public wrapper/re-export if external consumers truly need one).
Search for uses of `token_transformer::` outside the crate and either adjust
call sites to use the internal path (within the crate) or create a small,
explicit public facade function/type to re-export only the required symbols
rather than the entire module.

packages/web-platform/web-core-e2e/tests/reactlynx/basic-vw-vh-unit/index.jsx (1)

6-19: Consider removing the unnecessary fragment wrapper for consistency.

The <>...</> fragment wrapper around the single <view> element is unnecessary since there's only one child. The basic-rpx-unit/index.jsx test doesn't use a fragment wrapper for its single element.

♻️ Suggested simplification

 function App() {
   return (
-    <>
-      <view
-        id='target'
-        style={{
-          height: '50vh',
-          width: '50vw',
-          background: 'blue',
-        }}
-      />
-    </>
+    <view
+      id='target'
+      style={{
+        height: '50vh',
+        width: '50vw',
+        background: 'blue',
+      }}
+    />
   );
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@packages/web-platform/web-core-e2e/tests/reactlynx/basic-vw-vh-unit/index.jsx`
around lines 6 - 19, Remove the unnecessary JSX fragment in the App component:
update the App function (function App) to return the single <view id='target'
.../> element directly instead of wrapping it with the fragment (<>...</>), so
the component returns the single root element without the fragment for
consistency with basic-rpx-unit/index.jsx.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@packages/web-platform/web-core/src/main_thread/server/main_thread_server_context.rs`:
- Around line 35-37: The changes introduce main-thread-visible style
transformation flags (transform_vw and transform_vh) in the server context, but
there are no corresponding JS-side tests; add cases to element-apis.spec.ts that
cover the updated main-thread style-transformation behavior by exercising the
code paths that read transform_vw and transform_vh (and other modified
transformation logic in the same main-thread module) — create test elements,
apply styles that use vw/vh-based transforms, and assert the computed
styles/layout and any expected transform results to ensure the new flags behave
correctly from the JS side.

---

Outside diff comments:
In `@packages/web-platform/web-core/tests/element-apis.spec.ts`:
- Around line 1375-1391: The test's config passed to createServerElementAPI is
missing the now-required numeric callbacks transformVW and transformVH; update
the config object used in the 'create element infer css id from parent component
in SSR' test to include transformVW and transformVH properties (functions
returning numbers) so the config shape matches the new createElementAPI
expectations and the call to createServerElementAPI compiles.
- Around line 1461-1465: Call to wasmInstance.decode_style_info is missing the
two new boolean parameters transform_vw and transform_vh; update the invocation
(the encodedStyleInfo assignment) to include those two booleans (e.g., pass
false, false or the appropriate test variables) so the call matches the updated
signature: decode_style_info(encodedRawStyleInfo, undefined, true, transform_vw,
transform_vh).
- Around line 1413-1428: The test "create element wont infer css id if parent
css id is 0 in SSR" passes a config to createServerElementAPI but omits the
required transformVW and transformVH properties; add transformVW and transformVH
to the config object used in this test (the same properties used in the previous
SSR test) so the config matches the expected shape when calling
createServerElementAPI.

---

Nitpick comments:
In
`@packages/web-platform/web-core-e2e/tests/reactlynx/basic-vw-vh-unit/index.jsx`:
- Around line 6-19: Remove the unnecessary JSX fragment in the App component:
update the App function (function App) to return the single <view id='target'
.../> element directly instead of wrapping it with the fragment (<>...</>), so
the component returns the single root element without the fragment for
consistency with basic-rpx-unit/index.jsx.

In `@packages/web-platform/web-core/src/style_transformer/mod.rs`:
- Line 18: The module declaration `pub mod token_transformer` unnecessarily
exposes internal APIs; change it to a crate-private module by replacing the `pub
mod token_transformer` declaration with a private `mod token_transformer`, then
update any external references that relied on the public path (or add a minimal,
intentional public wrapper/re-export if external consumers truly need one).
Search for uses of `token_transformer::` outside the crate and either adjust
call sites to use the internal path (within the crate) or create a small,
explicit public facade function/type to re-export only the required symbols
rather than the entire module.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0a45efb0-299e-4fe1-b4be-019f1242d8ba

📥 Commits

Reviewing files that changed from the base of the PR and between 36b38eb and 48ea22e.

📒 Files selected for processing (33)

• .changeset/transform-rpx.md
• .changeset/transform-vw-vh-support.md
• packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts
• packages/web-platform/web-core-e2e/tests/reactlynx/basic-rpx-unit/index.jsx
• packages/web-platform/web-core-e2e/tests/reactlynx/basic-vw-vh-unit/index.jsx
• packages/web-platform/web-core/binary/client/client.d.ts
• packages/web-platform/web-core/binary/client/client_bg.wasm.d.ts
• packages/web-platform/web-core/binary/encode/encode.d.ts
• packages/web-platform/web-core/binary/encode/encode_bg.wasm.d.ts
• packages/web-platform/web-core/binary/server/server.d.ts
• packages/web-platform/web-core/binary/server/server_bg.wasm.d.ts
• packages/web-platform/web-core/css/index.css
• packages/web-platform/web-core/src/main_thread/client/element_apis/style_apis.rs
• packages/web-platform/web-core/src/main_thread/server/main_thread_server_context.rs
• packages/web-platform/web-core/src/style_transformer/inline_style.rs
• packages/web-platform/web-core/src/style_transformer/mod.rs
• packages/web-platform/web-core/src/style_transformer/token_transformer.rs
• packages/web-platform/web-core/src/style_transformer/transformer.rs
• packages/web-platform/web-core/src/template/template_sections/style_info/decoded_style_data.rs
• packages/web-platform/web-core/src/template/template_sections/style_info/raw_style_info.rs
• packages/web-platform/web-core/src/template/template_sections/style_info/style_info_decoder.rs
• packages/web-platform/web-core/tests/element-apis.spec.ts
• packages/web-platform/web-core/tests/template-manager.spec.ts
• packages/web-platform/web-core/ts/client/decodeWorker/cssLoader.ts
• packages/web-platform/web-core/ts/client/decodeWorker/decode.worker.ts
• packages/web-platform/web-core/ts/client/decodeWorker/types.ts
• packages/web-platform/web-core/ts/client/mainthread/LynxView.ts
• packages/web-platform/web-core/ts/client/mainthread/LynxViewInstance.ts
• packages/web-platform/web-core/ts/client/mainthread/TemplateManager.ts
• packages/web-platform/web-core/ts/client/mainthread/elementAPIs/createElementAPI.ts
• packages/web-platform/web-core/ts/server/decode.ts
• packages/web-platform/web-core/ts/server/deploy.ts
• packages/web-platform/web-core/ts/server/elementAPIs/createElementAPI.ts

👮 Files not reviewed due to content moderation or server errors (8)

• .changeset/transform-rpx.md
• packages/web-platform/web-core/ts/client/decodeWorker/cssLoader.ts
• .changeset/transform-vw-vh-support.md
• packages/web-platform/web-core/ts/client/mainthread/elementAPIs/createElementAPI.ts
• packages/web-platform/web-core/ts/client/mainthread/TemplateManager.ts
• packages/web-platform/web-core/css/index.css
• packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts
• packages/web-platform/web-core/ts/server/deploy.ts

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts`:
- Around line 404-408: Update the outdated/misleading comment that describes
container-query math to reflect the actual test setup and expectations: mention
that --vw-unit and --vh-unit are 10px so 50vw/50vh compute to 500px (matching
the assertions in expect(target).toHaveCSS('width','500px') and
expect(target).toHaveCSS('height','500px')), and remove the incorrect
container-query 25px/50px explanation; also remove the unnecessary await on the
synchronous page.locator(...) call (used to assign target) so the locator is
obtained without await.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: de39a139-7439-45ae-a79b-56b158eda07c

📥 Commits

Reviewing files that changed from the base of the PR and between 48ea22e and 1b8f7bc.

📒 Files selected for processing (3)

• packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts
• packages/web-platform/web-core/binary/client_legacy/client.d.ts
• packages/web-platform/web-core/binary/client_legacy/client_bg.wasm.d.ts

[coderabbitai]

Actionable comments posted: 1

♻️ Duplicate comments (1)

packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts (1)

407-415: ⚠️ Potential issue | 🟠 Major

Post-toggle assertions do not verify the intended behavior.

Line 414 and Line 415 (not 25px/not 50px) are too weak and may pass even when transform toggling is broken. Assert that the transformed 500px results are no longer present (or assert explicit expected values after disabling).

🔧 Suggested assertion update

-      await expect(target).not.toHaveCSS('width', '25px');
-      await expect(target).not.toHaveCSS('height', '50px');
+      await expect(target).not.toHaveCSS('width', '500px');
+      await expect(target).not.toHaveCSS('height', '500px');

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts` around lines 407
- 415, After disabling transforms via lynxView.evaluate (setting
node.transformVW = false and node.transformVH = false followed by
node.reload()), replace the weak negative assertions on
target.toHaveCSS('width','25px') and ('height','50px') with explicit assertions
that verify the transformed 500px values are no longer present (e.g., assert
target does not have width/height '500px') or assert the explicit expected
dimensions after disabling transforms; update assertions referencing target and
toHaveCSS so they validate the intended post-toggle dimensions rather than just
"not 25px"/"not 50px".

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/web-platform/web-core/tests/element-apis.spec.ts`:
- Around line 439-461: The tests call createElementAPI(...) with
transformVW/transformVH enabled but still assert raw 'vw'/'vh' CSS strings;
update the assertions to expect transformed values (or validate computed style)
instead of raw units. Locate tests using createElementAPI and __SetInlineStyles
(e.g., the test named "__SetInlineStyles with object and vw/vh when enabled" and
similar cases around lines referenced) and change
expect(targetStyle).toBe('width:50vw;height:100vh;') to assert the transformed
result produced when transformVW/transformVH are true (or retrieve computed
styles from the DOM and assert those), and apply the same fix to the other
affected tests that assert 'vw'/'vh'/'rpx' when transforms are enabled.

---

Duplicate comments:
In `@packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts`:
- Around line 407-415: After disabling transforms via lynxView.evaluate (setting
node.transformVW = false and node.transformVH = false followed by
node.reload()), replace the weak negative assertions on
target.toHaveCSS('width','25px') and ('height','50px') with explicit assertions
that verify the transformed 500px values are no longer present (e.g., assert
target does not have width/height '500px') or assert the explicit expected
dimensions after disabling transforms; update assertions referencing target and
toHaveCSS so they validate the intended post-toggle dimensions rather than just
"not 25px"/"not 50px".

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9217d863-8e71-484d-a79a-ed128af22d72

📥 Commits

Reviewing files that changed from the base of the PR and between c93127b and e0de618.

📒 Files selected for processing (2)

• packages/web-platform/web-core-e2e/tests/reactlynx.spec.ts
• packages/web-platform/web-core/tests/element-apis.spec.ts

[Huxpro]

SHHHHIP IT! ;)