-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
MutationObserver triggers changes on unchanged inline styles #3305
Comments
just-boris
added a commit
to just-boris/cssstyle
that referenced
this issue
Dec 12, 2021
just-boris
added a commit
to just-boris/cssstyle
that referenced
this issue
Dec 12, 2021
just-boris
added a commit
to just-boris/cssstyle
that referenced
this issue
Dec 12, 2021
domenic
pushed a commit
to jsdom/cssstyle
that referenced
this issue
Dec 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Basic info:
Minimal reproduction case
How does similar code behave in browsers?
https://jsbin.com/goripoqode/edit?html,js,console,output
In browsers, you will see only console message, caused by the first mutation. In JSDOM, there will be mutation callback on every
style
change, even if it produces the samecssText
.This causes infinite loops, if mutation observer updates styles on the node itself.
The text was updated successfully, but these errors were encountered: