Consider showing the "insert new paragraph" buttons regardless of widget location

[Reinmar]

📝 Provide a description of the improvement

I find situations like the one above confusing:

So, there's no button in this case... why? Because this image is anchored before the block quote.

That made me think a bit and I realised that I actually use <kbd>Enter</kbd> to start typing after widgets on many occasions – not only when there's no space after/before that widget.

Assuming that the button will show up only when my mouse pointer is near it, I think that it makes sense to have 2 buttons per every widget in the document. This will actually remove some code and make the editor faster too 😁.

---

If you'd like to see this improvement implemented, add a 👍 reaction to this post.

[oleq]

Maybe let's narrow this a little bit and show them always for floated objects?

[Reinmar]

Maybe let's narrow this a little bit and show them always for floated objects?

That would be one option.

But I reported this issue as the current behavior made me think that, in general:

• it may still be confusing for people why some buttons are displayed and some not – normal users may not get what the "tight, inaccessible" space that this feature is suppose to help with is,
• creating a new paragraph before/after any image in the content, regardless of its position is a really common case – e.g. after you drop an image into some document template (like here in GitHub Writer, when we use issue templates) – I want to start typing after the image, but there's a heading below it – the button would be one click solution.

[oleq]

I don't say no. I think it's worth checking. 

What I'm worried about, though, it that there will be too many UI elements visible at a time (some of them not absolutely necessary) and that will decrease the content/noise ratio and degrade the UX.

[oleq]

The PoC of this approach is on-line. RFC.

[neongreen]

I think the magic block buttons should just always be shown when a table/code block/etc is selected, period. Regardless if it's floating or not.

E.g. in this example technically I don't need a magic block to type after this image:

But I just tried it out and I found myself reaching for the magic block button instinctively, after using the magic block button just one time before, and felt a tinge of disappointment it wasn't there.

[oleq]

Good news then, @neongreen: we're planning on enabling these buttons for all block widgets in all situations in the next release. Stay tuned!