You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using crossorigin attribute on script to opt-out of default security feature of crossorigin="anonymous", it is possible to use either crossorigin: false or crossorigin: undefined to do this. However, when using undefined, only the script tag will be stripped of the attribute and not the corresponding preload tag.
When reading the source code for registry scripts, I learned that the "right" way to opt-out currently seems to be using false or null.
Considering how common it can be that the developers want to opt out from crossorigin="anonymous" default, both values should either work uniformly or the developer should be better informed of the differences between the possible falsy values.
🛠️ To reproduce
See description
🌈 Expected behavior
🌈
ℹ️ Additional context
No response
The text was updated successfully, but these errors were encountered:
🐛 The bug
When using
crossorigin
attribute on script to opt-out of default security feature ofcrossorigin="anonymous"
, it is possible to use eithercrossorigin: false
orcrossorigin: undefined
to do this. However, when usingundefined
, only the script tag will be stripped of the attribute and not the corresponding preload tag.When reading the source code for registry scripts, I learned that the "right" way to opt-out currently seems to be using
false
ornull
.Considering how common it can be that the developers want to opt out from
crossorigin="anonymous"
default, both values should either work uniformly or the developer should be better informed of the differences between the possible falsy values.🛠️ To reproduce
See description
🌈 Expected behavior
🌈
ℹ️ Additional context
No response
The text was updated successfully, but these errors were encountered: