fix(useCssVars): fix the loss of CSS variables during updates #9824
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixed #9821
During the
patchStyle
process, if a string type is passed, it will overwrite the entirecssText
, leading to the loss of theuseCssVars
variable. InuseCssVars
, I store CSS variables in a private property of the style, which is then collectively set tocssText
during thepatchStyle
process.I attempted to use a
MutationObserver
to monitor style changes in all child elements. However, in the scenario where we also need to listen to thechildList
of theparentNode
, I had to add anotherMutationObserver
within theparentNode
's observer to simultaneously monitor newly added child elements. This approach introduces complexity to the logic, so I opted for the current solution.