The breadcrumbs at the bottom (which you should let me move to the top) are crushed and hide most of their labels, whilst there’s extra space on the right.
Or reveal the entire label in a tooltip on hover if the breadcrumbs get squished?
Both please !
Great ideas thanks a bunch, we’ll take a look at this. Might not be ready for next release.
Howdy @bill_hodgson and @JvP,
Appreciate the thoughts here. The intent of providing an overflow is due to the nature of wanting to make as many of the breadcrumbs visible in the bar before scrolling horizontally in the parent container. If a user had even a couple breadcrumbs named something overly verbose like “Introduction Section for Corporate Staff” (and this does happen a lot), then you’d almost always find yourself scrolling horizontally to see things even in a smaller tree of Elements.
That being said, I spent some time revisiting this today as I love a good CSS puzzle and was hoping for some inspiration to find a middle ground where when space was available I could allow breadcrumbs to extend and then intelligently shrink only when I needed them to and when they meet a certain criteria (i.e. over a certain base width). Unfortunately, this particular problem wouldn’t be possible without the use of container queries, which have been talked about for many, many years now, but are only just now starting to come into the specs and are not widely supported. We attempted some solutions as well that fudged this with JavaScript, but they always ended up with some type of flash of content (breadcrumbs jumping around in size as you click through the interface, which is very distracting and feels broken).
I do think a compromise here is to add a tooltip for overflowing breadcrumbs, in addition to every so slightly bumping up the max width allowed. This gives a tiny bit more context until they overflow, and when they do, a label will be seen in the tooltip. Hopefully this is a good compromise and will improve the experience here all things considered.
Thanks!
2 Likes
Thanks Kory for taking a detailed look as always. Sounds like a good compromise to me 
Thanks for the feedback - your explanation makes sense. When can we expect RC2? 
@JvP and @bill_hodgson, no problem! Happy to look into it. We do not have word right now on RC2 but are pushing forward as always.