Hi @Hans Goudey (HooglyBoogly) is there a consensus among the UI team about this proposal?

For comparison this the 2.83, master and the patch panels side-by-side:

This is the solution proposed by Pablo and I believe Francesco. There's an alternative proposal which looks like this:

In D9235#230044, @Julian Eisel (Severin) wrote:

This is the solution proposed by Pablo and I believe Francesco.

Did they propose to remove the bread crumbs altogether?

There's an alternative proposal which looks like this:

We need @Pablo Vazquez (pablovazquez) to give feedback and make a decision together.

This is a no-brainer and should be in from day one I think. In fact it is what was proposed in T71185 as well.

The discussion on how to make the header more compact seems to be a separate issue (and the one presented here).

The pin is attached with the search, it looks like "pinning the search result". While resizing, it stays with the search, which reinforces this feeling.
Splitting the header into two halves, with label cropping and search disappearing (if there is not enough space) - it looks strange, it is not used in Blender, the user expects scrolling.

I think "bread crumbs" are important, for example Armature.003 > Armature.002 > Bone.001.

In D9235#230050, @Dalai Felinto (dfelinto) wrote:

Did they propose to remove the bread crumbs altogether?

Reading back the chat log - Removing this was proposed by Pablo and Harley, and even voted for by Hans and Nathan. Others didn't voice an opinion.
You could argue that the context this is supposed to add isn't that useful really. Might be misleading even - the data-block can be used by many other data-blocks, there can be many more data-paths a data-block is in.

I don't mind it too much and leave it up to the team.
However it does seem like we shouldn't make such a change that late in the release cycle. We shouldn't risk having to revert something in bcon3, just because things got rushed at the end and not user tested long enough. That's why I also made the call to not push any further Outliner changes that late.

There is redundancy in the breadcrumbs, for example for meshes it's not so useful to have the mesh both in the breadcrumbs and a datablock selector. But this patch does not solve that redundancy, it still repeats the mesh datablock and leaves out the object, which is the interesting part. When you use the mesh datablock selector, you are changing the object, and I think there should be some indication of that.

I think simply moving the pin icon to the breadcrumbs again is better than what is being proposed here, and seems like the right solution for 2.91 to me.

There could be a more compact design. Maybe the pin icon could be next to the datablock selector, and then only the second to last item from the breadcrumbs could be shown. There is no datablock selector for scenes or view layers, so those would need to be added.

Here's another alternative I'd actually prefer (if we decide to make the change to crop the data-path): It makes the label and the icon a clickable field together, moves the icon to the left (like usual for such clickable elements) and I think behaves nicer on area resizing.

I personally prefer this:

In D9235#230061, @Julian Eisel (Severin) wrote:

Search is nicely aligned, context pinning is next to the context name, and breadcrumbs only show the appropriate datablock (which could expand the full path on mouse over).

However, since we are already at bcon3, let's go with the more conservative option and keep this in the back of our heads for a more fleshed out re-design of the breadcrumbs system. Which is something we need to do anyway as more parts of Blender will rely on node groups (likely nested) in the future.

In D9235#230044, @Julian Eisel (Severin) wrote:

+1