refactor: favor directly modifying DOM attributes over using setAttribute()
#598
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.
According to https://stackoverflow.com/a/57633533:
setAttribute()
invokes the HTML parser, which can trigger a CSP violation.This PR refactors style element construction/manipulation to not leverage
setAttribute()
, where applicable.See comparison of this behavior between the main branch and this one:
Screen.Recording.2021-02-16.at.5.17.26.PM.mov
Fixes #595