This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
fix(head): case http-equiv correctly
#7190
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for nuxt3-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
🔗 Linked issue
❓ Type of change
📚 Description
Currently, when using the
Metacomponent, it's not possible to provide a value forhttp-equiv. This is becausehttp-equivgets turned tohttpEquiv, from Vue prop passing.httpequivis the final DOM result and it's not honoured by browsersThis PR simply swaps out the key for the correct one, I beleive this will be a temporary fix if unjs is working on a dom handling package.
Reproduction
https://stackblitz.com/edit/nuxt-starter-jdegdy?file=app.vue
📝 Checklist