TinyMCE per block prototype: Add image with caption block

[youknowriad]

No description provided.

[aduth]

Do you think this ought to be a separate block or an option to the existing base image blocks?

Related is how we'll need to support existing content which may include [caption] shortcodes that should be treated as equivalent blocks, however we decide to implement them.

[youknowriad]

Do you think this ought to be a separate block or an option to the existing base image blocks?

I don't have a final answer for now. I decided to go separate for now to show an image without any caption text field which changes the way the keyboard (arrows, enter, backspace) behaves. I can answer with another question.

How do we "enable" a caption for a simple image block? In case of a separate block, we could use the "transform" API (same as switching between paragraph and heading for example). but what if it's the same component, should we always show the caption input?

[caption] shortcodes that should be treated as equivalent blocks

My personal answer to that, is to limit the way the editor stores the post content to one unique way. So maybe the answer to this question is having the grammar parse those different ways of writing the same block into the same structure, but serializing this data would use one way only.

[aduth]

but what if it's the same component, should we always show the caption input?

Per the current mockup, I think this is what to expect, yes (cc @jasmussen).

My personal answer to that, is to limit the way the editor stores the post content to one unique way.

We'll definitely need to think on this. I agree ideally if we settle on a block syntax, that should be the recommendation for all new posts. If that were the case, we'd certainly need to be able to detect and upgrade the previous syntax to the new variation, if only in the context of the editor itself. The most contentious question might be: If we detect old syntax, should we save it as new syntax if the user updates the post? What impact does this have on plugins that, for example, hook into and modify a [caption] shortcode?

[jasmussen]

Thanks for the ping @aduth.

How do we "enable" a caption for a simple image block? In case of a separate block, we could use the "transform" API (same as switching between paragraph and heading for example). but what if it's the same component, should we always show the caption input?

We will likely want captions for lots of blocks. I can easily imagine inserting video with a caption, or even a code block with a caption. Which blocks might need a dedicated caption vs. just a single linebreak with a simple text, that's up for discussion. Maybe best discussed in #16.

UI-wise, we could show the caption input field only when the block is selected? I.e. Insert an image and move on, no caption field is shown. Click the image later on, and the caption field "pops out" below.

CC: @mtias