I have a textarea
component that include html tag
and I want to get html
in edit mode in this component. I use Laravel
to generate html.
<template>
<div>
<textarea
:value="content"
:name="name"
:id="id">
<slot></slot>
</textarea>
</div>
</template>
In blade page I used to this component:
<my-component>
<p class="textbox">hello world</p>
</my-component>
when I put this component in page show me tag <slot></slot>
in textarea. What should I do? Do you have any solution for my need?
thanks
<textarea>
components are treated as static by the Vue renderer, thus after they are put into the DOM, they don't change at all (so that's why if you inspect the DOM you'll see <slot></slot>
inside your <textarea>
).
But even it if they did change, that wouldn't help much. Just because HTML elements inside <textarea>
s don't become their value. You have to set the value
property of the TextArea element to make it work.
Anyway, don't despair. It is doable, all you need to overcome the issues above is to bring a small helper component into play.
There are many possible ways to achieve this, two shown below. They differ basically in how you would want your original component's template to be.
<textarea>
into <textarea-slot>
componentYour component's template would now become:
<template>
<div>
<textarea-slot
v-model="myContent"
:name="name"
:id="id">
<slot></slot>
</textarea-slot>
</div>
</template>
As you can see, nothing but replacing <textarea>
with <textarea-slot>
changed. This is enough to overcome the static treatment Vue gives to <textarea>
. The full implementation of <textarea-slot>
is in the demo below.
<textarea>
but get <slot>
's HTML via <vnode-to-html>
componentThe solution is to create a helper component (named vnode-to-html
below) that would convert your slot's VNodes into HTML strings. You could then set such HTML strings as the value
of your <textarea>
. Your component's template would now become:
<template>
<div>
<vnode-to-html :vnode="$slots.default" @html="valForMyTextArea = $event" />
<textarea
:value="valForMyTextArea"
:name="name"
:id="id">
</textarea>
</div>
</template>
The usage of the my-component
stays the same:
<my-component>
<p class="textbox">hello world</p>
</my-component>
Vue.component('my-component', {
props: ["content", "name", "id"],
template: `
<div>
<textarea-slot
v-model="myContent"
:name="name"
:id="id">
<slot></slot>
</textarea-slot>
<vnode-to-html :vnode="$slots.default" @html="valueForMyTextArea = $event" />
<textarea
:value="valueForMyTextArea"
:name="name"
:id="id">
</textarea>
</div>
`,
data() { return {valueForMyTextArea: '', myContent: null} }
});
Vue.component('textarea-slot', {
props: ["value", "name", "id"],
render: function(createElement) {
return createElement("textarea",
{attrs: {id: this.$props.id, name: this.$props.name}, on: {...this.$listeners, input: (e) => this.$emit('input', e.target.value)}, domProps: {"value": this.$props.value}},
[createElement("template", {ref: "slotHtmlRef"}, this.$slots.default)]
);
},
data() { return {defaultSlotHtml: null} },
mounted() {
this.$emit('input', [...this.$refs.slotHtmlRef.childNodes].map(n => n.outerHTML).join('\n'))
}
});
Vue.component('vnode-to-html', {
props: ['vnode'],
render(createElement) {
return createElement("template", [this.vnode]);
},
mounted() {
this.$emit('html', [...this.$el.childNodes].map(n => n.outerHTML).join('\n'));
}
});
new Vue({
el: '#app'
})
<script src="https://unpkg.com/vue"></script>
<div id="app">
<my-component>
<p class="textbox">hell
o world1</p>
<p class="textbox">hello world2</p>
</my-component>
</div>
Breakdown:
<slot>
s into VNode
s and makes them available in the this.$slots.SLOTNAME
property. The default slot, naturally, goes in this.$slots.default
.<slot>
(as VNodes in this.$slots.default
). The challenge now becomes how to convert those VNodes to HTML String? This is a complicated, still open, issue, which may get a different solution in the future, but, even if it ever does, it will most likely take a while.template-slot
and vnode-to-html
) use Vue's render function to render the VNodes to the DOM, then picks up the rendered HTML.<script>
tags.vnode-to-html
returns as an event that should be picked up by the parent (my-component
) which uses the passed value to set a data
property that will be set as :value
of the textarea
.textarea-slot
declares itself a <textarea>
, to the parent doesn't have to. It is a cleaner solution, but requires more care because you have to specify which properties you want to pass down to the <textarea>
created inside textarea-slot
.However possible, it is important to know that Vue, when parsing the declared <template>
into <slot>
s, will strip some formatting information, like whitespaces between top-level components. Similarly, it strips <script>
tags (because they are unsafe). These are caveats inherent to any solutions using <slot>
s (presented here or not). So be aware.
Typical rich text editors for Vue, work around this problem altogether by using v-model
(or value
) attributes to pass the code into the components.
Well known examples include:
They all have very good documentation in their websites (linked above), so it would be of little use for me to repeat them here, but just as an example, see how codemirror uses the value
prop to pass the code:
<codemirror ref="myCm"
:value="code"
:options="cmOptions"
@ready="onCmReady"
@focus="onCmFocus"
@input="onCmCodeChange">
</codemirror>
So that's how they do it. Of course, if <slot>
s - with its caveats - fit your use case, they can be used as well.
The short answer is NOT POSSIBLE
Your slot is put inside an textarea tag. Textare tag is only able to display the text content on its box.
So in the case you want a kind of "HTML edit mode", you may looking for an WYSIWYG editor, I recommend you can use CKEditor for VueJS, the editor even will allow you to direct edit HTML code
https://ckeditor.com/docs/ckeditor5/latest/builds/guides/integration/frameworks/vuejs.html
Your HTML
<div id="app">
<ckeditor :editor="editor" v-model="editorData" :config="editorConfig"></ckeditor>
</div>
Your Component
const app = new Vue( {
el: '#app',
data: {
editor: ClassicEditor,
editorData: '<p>Editable Content HTML</p>',
editorConfig: {
// The configuration of the editor.
}
}
} );
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With