From 2322328e2eb4539a8753094ce798e56e7801d90c Mon Sep 17 00:00:00 2001 From: Ian Storm Taylor Date: Sun, 17 Jul 2016 13:39:30 -0700 Subject: [PATCH] add faq --- docs/concepts/faq.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 docs/concepts/faq.md diff --git a/docs/concepts/faq.md b/docs/concepts/faq.md new file mode 100644 index 000000000..4fc8a2030 --- /dev/null +++ b/docs/concepts/faq.md @@ -0,0 +1,15 @@ + +# FAQ + +A series of common questions people have about Slate: + +- [How come content is pasted as plain text?](#how-come-content-is-pasted-as-plain-text) + + +#### How come content is pasted as plain text? + +One of Slate's core principles is that, unlike most other editors, it does **not** prescribe a specific "schema" to the content you are editing. This means that Slate's core has no concept of "block quotes" or "bold formatting". + +For this most part, this leads to increased flexbility without many downsides, but there are certain cases where you have to do a bit more work. Pasting is one of those cases. + +Since Slate knows nothing about your schema, it can't know how to parse pasted HTML content (or other content). So, by default whenever a user pastes content into a Slate editor, it will parse it as plain text. If you want it to be smarter about pasted content, you need to define an [`onPaste`](../reference/components/editor.md#onpaste) handler that parses the content as you wish.