Skip to content

fix(useCssVar): avoid untarget style pollution #4841

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

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

ArthurDarkstone
Copy link
Contributor

@ArthurDarkstone ArthurDarkstone commented Jun 27, 2025

Before submitting the PR, please make sure you do the following

  • Read the Contributing Guidelines.
  • Read the Pull Request Guidelines.
  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
  • Ideally, include relevant tests that fail without this PR but pass with it.
⚠️ Slowing down new functions

Warning: Slowing down new functions

As the VueUse audience continues to grow, we have been inundated with an overwhelming number of feature requests and pull requests. As a result, maintaining the project has become increasingly challenging and has stretched our capacity to its limits. As such, in the near future, we may need to slow down our acceptance of new features and prioritize the stability and quality of existing functions. Please note that new features for VueUse may not be accepted at this time. If you have any new ideas, we suggest that you first incorporate them into your own codebase, iterate on them to suit your needs, and assess their generalizability. If you strongly believe that your ideas are beneficial to the community, you may submit a pull request along with your use cases, and we would be happy to review and discuss them. Thank you for your understanding.


Description

Additional context

fix: #4828

@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Jun 27, 2025
@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. and removed size:S This PR changes 10-29 lines, ignoring generated files. labels Jun 27, 2025
@ilyaliao ilyaliao changed the title Fix useCssVar untarget style pollution fix(useCssVar): avoid untarget style pollution Jun 28, 2025
ilyaliao
ilyaliao previously approved these changes Jun 28, 2025
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jun 28, 2025
@43081j
Copy link
Collaborator

43081j commented Jun 28, 2025

does this mean there's no way to get back to the fallback?

maybe we should just treat null and undefined differently

if the target is null, someone must've explicitly set it to that or failed to find the element. if it is undefined, they just didn't set a target

so we can just fallback when it is undefined?

@ilyaliao
Copy link
Member

ilyaliao commented Jun 29, 2025

Yes, another issue is that when the target gets replaced, the new one might not have been rendered yet.
(Also, I don’t think we should cause side effects inside a computed)

@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. and removed size:M This PR changes 30-99 lines, ignoring generated files. labels Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm This PR has been approved by a maintainer size:L This PR changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG | useCssVar | The css variables are added to document.documentElement when the initial value of target is undefined
4 participants