fix(compiler-ssr): ensure v-text renders correctly with custom directives in SSR output #12311
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.
Fixes #12309:
v-textnow functions correctly in SSR, even when other custom directives are applied to the same element.The fix ensures that when
v-textis present, it takes priority overtextContentandinnerHTMLprovided by other directives. This prevents conflicts in the SSR output, allowingv-textto render as expected.v-htmlalready behaves correctly by directly modifyingrawChildrenMap, so this change alignsv-textbehavior with that ofv-htmlin SSR scenarios.