Meta tags are "deduped" based on property name only
yp0011 opened this issue · 8 comments
According to https://ogp.me/ "If a tag can have multiple values, just put multiple versions of the same tag on your page."
In my use case I want to add multiple tags for the video pages of my website and I am adding these values to the meta array. The issue is that only 1 of the properties is added due to the fact that the property names are the same.
I have tested this by adding a suffix to each property name and all of the elements are added, although they are no longer valid OG tags.
<meta property="og:video:tag1" content="Bene Gesserit">
<meta property="og:video:tag2" content="Blade Runner 2049">
<meta property="og:video:tag3" content="Coming Soon">
Currently I only get
<meta property="og:video:tag" content="Coming Soon">
The desired outcoume would look like below :
<meta property="og:video:tag" content="Bene Gesserit">
<meta property="og:video:tag" content="Blade Runner 2049">
<meta property="og:video:tag" content="Coming Soon">
I would suggest that a check on the content property value is performed during the deduplication process in order to allow for the desired output as above.
You can use key attribute to avoid this.
You can use
keyattribute to avoid this.
Not sure how I missed this, although it does seem a little bit redundant if the content could be used for this purpose?
Not sure how I missed this, although it does seem a little bit redundant if the
contentcould be used for this purpose?
yeah that seems like a good idea
After 0.7.3 I have the following lines from index.html dissappearing in the final build.
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
I guess this is related to this issue.
As of @vueuse/head@v0.7.12, should I make reproduction repo?
What issue are you having exactly? Reproduction repo would be helpful
Thanks for quick attention, but after giving it few hours I found out that there was a bug in i18n-module
Going to close this as the above is unrelated and the main issue is resolved.