Just to mention, some users who've downloaded our and used builds have requested to customize these panels even further, either default closed or open, or to show/hide. The user option for these file browser panels should remain.

Tested, all green from me.

Can confirm, trying to set from Right Click menu on the toolshelf operators goes to wm.

Can confirm the issue, and the fix here.

Looks good. I was needing this the other day, would improve the UX a lot there.

Agree, with a user prop as an option, allow automatically adding the override if the data is linked to a clear and hassle free UX (drag and drop then use - not drag, drop, override, then use)

Removing it is a bandaid solution to the code issues and doesn't address the UX if at all.

Thanks for taking a look at it. When/how will it become a task to get code commit to? Do you track code commits to feature requests somewhere?

This has an issue, now the background colour is decoupled from the theme property of the Node Group colour. This means... group nodes don't have any colour coding - and that prop is now useless. This also clashes with the grid colour, as that doesn't change with the background.

Would this be a part of the "Everything Nodes" development cycles?

I think this is an excellent solution to a community UX debate.

Bump, this needs some polish.

Ping. What is the final verdict for this patch?

Solid line are easier to read and less noise. I would opt to color coding.

Take note, my screen captures are from a custom build of Blender with custom icons.

Wow, the code looks like a small change. Does this apply throughout the entire UI?

Yes, clicking on the right click then sub menu, or going into a sub menu is a little tricky. Making it consistent with the file browser here would make sense.

Suggested expected UX per editor, which can be divided into two levels of UX, the intuitive and the granular:

Can confirm, search doesn't work with Collections. Mesh data yes. Material nodes can be limited.

Is this like an asset reviewer standalone?

This is a pretty big spanner in the UX of joining and merging and applying geometry from instances. If there are no UVs post the modifier - but the instance has one, they should be applied when applied, it is expected behaviour to preserve the legacy UV's without needing to work around.

Proposal B has my vote - even just an unused colour that says "Undefined: will adapt to what you plug in". Not sure about the picker readout proposal of E though, I think the readout should be dynamic to what you plug in.

Bump, will this be implemented for 3.0? I certainly hope so! It looks practically done.