fix: skip calling setAttribute on unchanged attr in diffProps #1691
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.
There’s a bug (?) in Chrome where dynamically added CSS rules (via
insertRule
) get dropped if you callstylesheet.setAttribute('type', 'text/css')
and the type is alreadytext/css
. Firefox does not drop these rules if the stylesheet already hastype="text/css"
and you try to set the attr again.Note: this is specifically for when the stylesheet already has
type="text/css"
and we try to callsetAttribute('type', 'text/css')
. Callingstylesheet.setAttribute('some-other-attr', ‘foo')
does not drop the styles.Here is a script you can paste into the Chrome’s browser console to see the styles getting dropped