Skip to content

feat(react/worklet): add getComputedStyle to Element #1166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

f0rdream
Copy link
Collaborator

This commit introduces the getComputedStyle method to the Element class in the worklet runtime. This method allows developers to retrieve the computed styles of an element, which is essential for dynamic styling and layout calculations. The implementation calls the underlying __GetComputedStyle API and includes the necessary type definitions to ensure type safety.

This commit introduces the `getComputedStyle` method to the `Element` class in the worklet runtime. This method allows developers to retrieve the computed styles of an element, which is essential for dynamic styling and layout calculations.

The implementation calls the underlying `__GetComputedStyle` API and includes the necessary type definitions to ensure type safety.
Copy link

changeset-bot bot commented Jun 26, 2025

⚠️ No Changeset found

Latest commit: e50c650

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@f0rdream f0rdream marked this pull request as draft June 26, 2025 06:32
Copy link

codspeed-hq bot commented Jun 26, 2025

CodSpeed Performance Report

Merging #1166 will not alter performance

Comparing f0rdream:imperative_handle (e50c650) with main (b8a1122)

Summary

✅ 10 untouched benchmarks

Copy link

relativeci bot commented Jun 26, 2025

React Example

#2163 Bundle Size — 233.19KiB (0%).

e50c650(current) vs b8a1122 main#2157(baseline)

Bundle metrics  no changes
                 Current
#2163
     Baseline
#2157
No change  Initial JS 0B 0B
No change  Initial CSS 0B 0B
No change  Cache Invalidation 0% 0%
No change  Chunks 0 0
No change  Assets 4 4
No change  Modules 152 152
No change  Duplicate Modules 60 60
No change  Duplicate Code 45.81% 45.81%
No change  Packages 2 2
No change  Duplicate Packages 0 0
Bundle size by type  no changes
                 Current
#2163
     Baseline
#2157
No change  IMG 145.76KiB 145.76KiB
No change  Other 87.43KiB 87.43KiB

Bundle analysis reportBranch f0rdream:imperative_handleProject dashboard


Generated by RelativeCIDocumentationReport issue

Copy link

relativeci bot commented Jun 26, 2025

Web Explorer

#2153 Bundle Size — 257.95KiB (0%).

e50c650(current) vs b8a1122 main#2147(baseline)

Bundle metrics  Change 1 change
                 Current
#2153
     Baseline
#2147
No change  Initial JS 140.07KiB 140.07KiB
No change  Initial CSS 31.82KiB 31.82KiB
No change  Cache Invalidation 0% 0%
No change  Chunks 4 4
No change  Assets 4 4
Change  Modules 206(+0.49%) 205
No change  Duplicate Modules 15 15
No change  Duplicate Code 3.41% 3.41%
No change  Packages 4 4
No change  Duplicate Packages 0 0
Bundle size by type  no changes
                 Current
#2153
     Baseline
#2147
No change  JS 226.13KiB 226.13KiB
No change  CSS 31.82KiB 31.82KiB

Bundle analysis reportBranch f0rdream:imperative_handleProject dashboard


Generated by RelativeCIDocumentationReport issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant