-
Notifications
You must be signed in to change notification settings - Fork 247
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
Booleanish behaviour of attributes like crossorigin not supported #447
Comments
Thanks for the report. Have moved this to the vue-meta repo because its a vue-meta issue. Vue-meta maintains a list of attributes which are boolean attributes. Seems that crossorigin is not listed because its not really a boolean attribute like the others, its just that if you omit an explicit value it fallsback to a default one. Dont think we can add crossorigin just to the list, because that list is for explicit boolean attributes only. Maybe we need a second list of booleanish attributes. |
You can always use empty string as a value for an attribute you want to be rendered as a booleanish. This link It may be more a hack than a feature till it is not mentioned in the documentation. Should I fix this by editing documentation? What do you think? |
That is not correct. This is being output:
Sadly that hasn't the desired effect. |
@luksak Unless this MDN page is incorrect, using |
@pimlie Ah ok. Thanks for clarifying. |
Version
v2.9.2
Reproduction link
https://codesandbox.io/s/codesandbox-nuxt-hm0ch
Steps to reproduce
When creating a new link with
crossorigin
value, and setting its value totrue
, attribute renders with value.View page source and search for
crossorigin
What is expected ?
Boolean attributes should not have value
What is actually happening?
Boolean attributes renders with value
The text was updated successfully, but these errors were encountered: