Drop down in bread crumbs should be after the parent node ( crumbtrail)

[lordyavin]

What happened? I always have problems to click/hover the right arrow in the bread crumbs to navigate to another node.

What you expected: Intuitively I expect the listing of children after (right of) the parent node.

[brendanheywood]

+1 from @nicHoch

[brendanheywood]

+1 from @ajlowndes from https://github.com/theCrag/website/issues/3034

What happened? In the breadcrumbs area, the dropdown arrows are to the left of the name of the area you are referencing. Should be to the right for better readability.

What you expected: If I am in Australia > Victoria > Melbourne and Surrounds > Camels Hump, and I want to choose an area INSIDE Camel's Hump (say "Omega Block area") then I would expect to click the '>' arrow to the RIGHT of the title "Camel's Hump". Instead I need to click the arrow to the left, which doesn't make as much sense.

[brendanheywood]

For the record when I implemented this I did consider both ways, and there are plenty of examples in the wild of this being done both ways. The main reason I went with this way is that a normal crumbtrail never has an arrow to the right of the last item and it seemed weird to have an extra arrow there. Bugs like this are tricky to get a feel for because you only hear from those that don't like it but possibly the silent majority prefer it as is.

[lordyavin]

@brendanheywood please post some links to samples. Actually I never saw bread crumbs implemented alike.

[brendanheywood]

Here is an example with the arrow on the right which shows siblings not children:

https://painwise.org/be-informed/pain-treatment-options/

Regardless, I think for when we get to this I will be leaning towards:

• [ ] not adding an arrow to the right of the current node
• [ ] making the whole crumb item hover not just the arrow

I think this should make most people happy?

[ajlowndes]

I think to show sibling nodes, animate both the word and the arrow to it's right. That seems more robust. So in the above picture from @lordravin, animate all of "Outdoors >" to show the list "Linnie X".

[lordyavin]

Don't see any change to the breadcrumbs on the new design test (https://brendan.thecrag.com).

[brendanheywood]

I wasn't planning on addressing this in the new design. I did a prototype of making the dropdowns appear when you hover over the name (as opposed to just the arrow and regardless of which side it is one) but it's not great because then it's almost impossible to move your mouse from the top of the screen down into the page without triggering a big hover which gets in the way of what you really wanted to do. But this could be fixed with a slight hover delay but that also means redoing it all as js instead of css. This probably needs to happen anyway at some point, I need to redo all the dropdown menu buttons (eg the action menu's) so they work better on mobile.

[Mdemaillard]

Merging from #2544

From desktop perspective only: a hover on a node should show its daughter on dropdown, consistent everywhere, because nodes are easier to target than arrows.

BUT for mobile hover is bad (and precise targeting as well, doh).

So i would say: 1 click on a node opens the drop down, a second click targets the node itself. Forget the arrows.

[rouletout]

Obsolete since re-design, closing

[lordyavin]

Which re-design? For the current design this is not fixed or even changed.

[rouletout]

The one a few years back - these dropdowns do not exist anymore...

[lordyavin]

A screenshot taken seconds ago:

[rouletout]

Nice, wasn't even aware that we still have that :-)

But is this really an issue? I feel this behaviour is very intuitive as it uses the breadcrum as title for the list it opens....

[lordyavin]

For me it is. I don't no other UX that renders like theCrags breadcrumbs and hover events ;-)