#Node embed vs block embed

1 messages · Page 1 of 1 (latest)

jade cliff
#

Not sure if this is intentional, but there is a difference between ref counts between MD embeds and DB embeds.

In DB version, the node reference itself is counted, so you always see a counter with at least 1 when embedding a node.

In the MD version, a block reference on the same page didn't create a counter.

I think the old MD behaviour is cleaner, when I'm referencing a node, I don't need to see that very reference in the counter, I'm rather interested in other references.

Might go against a principle that an embedded node should appear the same in every context though.

#

There are some other UX issues with references too.

It's cool that highlighting one of the references highlights the others too. But when I e.g. click Del here, it deletes either the nodes below (if expanded) or the text content of the node (which creates a blank page error). It seems the only way to remove the reference is to right-click on the link icon and delete it from the context menu.

In the MD version, deleting a block ref only deleted that references and no content from the actual block. I think most people rather want that when deleting?

#

Finally, editing references does not feel great.

When I hit Enter and Tab below a regular node, I can start typing right away.

When I do the same below a node reference, the experience differs whether the node is collapsed (it's just blank and I don't know what happens) or expanded (I see the nodes below the reference but cursor is not focused, so need to click before I can start typing).