@William Reynish (billreynish) Could you please have a look.

This is due to the fact that deleting collections and objects are two different operators, and Blender doesn't know which one to use automatically. It's a todo:

https://developer.blender.org/T67462

I believe @Zachman is working on a fix for this issue.

Yes obviously it's a duplicate, sorry for that. But that's from July 2019

Why don't you implement that two clicks to fix it in the meantime with the workaround solution. That's broken since month and needs seconds to fix. Maybe a more elegant solution is somewhere around the corner.

But I don't get why so simple fixes get suspended.

@Debuk (Debuk) perhaps @Zachman could chime in to clarify how hard (or not) this would be to fix in the Outliner. It's certainly super annoying, and an issue lots of users face.

@William Reynish (billreynish): Hi William, yes it's certainly annoying. And it's like that for no reason.

Sure would it be somehow interesting to know when this topic is treated by him.

But to me that's not the point. This is lying around since last July, it's wrong to assume that it will be solved very soon.

What I tried to say is, it's in your hands to change these two shortcuts to "release" as proposed and solve this meanwhile until whatever change is done inside the outliner. This change is so minimal that it doesn't conflict with his development.

Couldn't you write him a note into his todo task that you changed them to release and that he should switch it back while he's coding it?

Hi @Debuk (Debuk), I definitely had hoped to work on this sooner, but as a university student life got in the way :(

I agree that this issue is very frustrating. A quick solution like you said is to add outliner_object_operation to all the keymaps under release for both X and Delete keys. That is fine to me (wonders what @William Reynish (billreynish) thinks) because I think a proper solution would take time.

Hi @Zachman, no worries. I know pretty well how it was during that time. Thanks for your valuation.

@William Reynish (billrey) What do you think of this workaround solution?

In my opinion assigning one for press and one to release sounds like a bad hack, which can cause other issues and conflicts. There's also a danger that the issue is then never properly addressed. I would rather see this done right, so that there is just a single delete operator in the Outliner which is context sensitive. Hopefully it's not a massive project to do this, once a developer is working on it.

@William Reynish (billrey) I can see the reasoning, but as @Zachman is also engaged to get this done, I'd wish blenders policy to treat things like this would rather consider that there are people out there using blender as part of their productive environment, than judging on if something feels like a hack.