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
If there are multiple top-level Vue-components (e.g. two apps or 1 app with off-document components) then the meta data will be overwritten completely when each app updates with the data (or lack of) of that vue app only. Eg in the case of off-document components which dont specify any metainfo , this means that all metadata is removed from the webpage once the off-doc component is updated
Vuetify 2.0 will use off-document components for eg overlays.
Proposal:
Identify the origin app of each metadata tag by using this.$root._uid as value for data-${attribute:=vue-meta} (this root uid probably needs to be stored separately on ssr)
Metadata with a $tagIDKeyName are listed under special value -1
If one of the app updates:
only replace/remove values specified by the corresponding app identifier
metadata tags with a $tagIDKeyName can be overwritten by any app
Disadvantages:
There will be no general merge of metadata of different apps, so its possible to generate non-validating html which contains more then one of the same tag while the spec specify that tag should be unique. Eg its up to the user to solve the issue of two title tags being added if both apps specify a title.
The title is a bad example as we update that on the client with document.title. So the title will always be set to the title of the last app that updated its metadata
Reported by @aldarund on discord.
If there are multiple top-level Vue-components (e.g. two apps or 1 app with off-document components) then the meta data will be overwritten completely when each app updates with the data (or lack of) of that vue app only. Eg in the case of off-document components which dont specify any metainfo , this means that all metadata is removed from the webpage once the off-doc component is updated
Vuetify 2.0 will use off-document components for eg overlays.
Proposal:
this.$root._uid
as value fordata-${attribute:=vue-meta}
(this root uid probably needs to be stored separately on ssr)$tagIDKeyName
are listed under special value-1
$tagIDKeyName
can be overwritten by any appDisadvantages:
Eg its up to the user to solve the issue of two title tags being added if both apps specify a title.The title is a bad example as we update that on the client with
document.title
. So the title will always be set to the title of the last app that updated its metadata@manniL @atinux @pi0 would appreciate your insights on this
The text was updated successfully, but these errors were encountered: