I think the team knows about this from a conversation on Discord. It looks like the same thing to me, but in case it’s a little different from what was discussed, I got your back with reproduction steps, Cristiano.
If the behavior change was intentional, then I think it should at least be separated from ‘smart list’ in settings and have it’s own toggle, as that would then constitute a quite distinct feature. But then is should likely also apply to normal lists (i.e. ‘- example’), so there is a bug here anyway.
I got the impression kepano saw that as a bug when he said, "you should be able to move the parent bullets up and down in a way that maintains the markup " (Discord) But perhaps he meant that differently, as a different issue was under discussion.
But I initially also thought it was happening due to being a loose list, which made sense to me. (and is why I pointed it out in context of trying to move a nested item rather than moving the parent item).
The behavior you posted about, where the blank line seems to come along for the ride as if it were nested, is what I was under the impression was seen as a bug. (But again, I could have misinterpreted. Which is why I added reproduction steps, in case it’s seen the way WhiteNoise said.) Personally, I think yours is a bug only in that it’s unintuitive, even if not technically incorrect.
The topic you linked to, however, about moving nested items in general, is listed in the changelog as intentional.
If you have a Discord account and your OMG insider badge, check out the link I put above. If you can’t access it, I can send you a screenshot of it—let me know. (I don’t whether it’d be frowned upon to paste it here.)
All of the smart list additions are very contrary to how I’d like it to behave. And to what works in my workflow. But (again, just personally; I totally get if you disagree) I now think it makes sense to be included in Smart lists.
A feature request to allow selective enabling of the different Smart list features might be the way to go for you?
My route: I’ve disabled Smart lists and will try to add auto-numbering to my personal plugin, and maybe some auto-indentation, without any of the other Smart list features.
I get the moving nested items, I think that is a good feature. But I don’t get what this has to do with this new behavior about empty lines. @WhiteNoise what do you mean by eating into the empty line?
My workflow is uses tasks groped logically with an empty space between them:
* [ ] Read
* [ ] Work
* [ ] Study 1. pom
* [ ] Study 2. pom
* [ ] Drink water
If I now want to move the “Work” item into the lower group, expecting this after moving work down:
* [ ] Read
* [ ] Work
* [ ] Study 1. pom
* [ ] Study 2. pom
* [ ] Drink water
But moving it down now moves “Study 1. pom” up into the first group additionally, and the empty space stay. Actual:
* [ ] Read
* [ ] Study 1. pom
* [ ] Work
* [ ] Study 2. pom
* [ ] Drink water
Turning off Smart lists fixes it, so I think the change comes from that feature. Sadly that also disables important features line making a newline stay a checklist item.
Is this workflow intentionally no longer possible now?
We are open to adjustments.
If you have suggestions, open a FR, esplicitely write a list, where the cursor is the command you call. Add what is happening now and what you think should happen.
To me, this is clearly a bug rather than a feature request. Previous versions of Obsidian handled this behavior correctly, but now it works differently.
The new line-moving behavior feels quite unusual, and I haven’t seen any other text editor handle checkboxes this way. This inconsistency is confusing for users, who may not know whether the behavior is intentional or simply a bug.
I believe line-moving commands should behave consistently, regardless of whether a line contains a checkbox or not, as users naturally expect.
