Replies: 1 comment 1 reply
-
Apologies for the delay in getting to this! I suspected as soon as you suggested it that a disclosure triangle would be a bit too much, given that we need to disclose two dropdowns, not just one. Putting another triangle next to the breadcrumb triangles, and it is: Even if we played with colour/transparency, I think this many triangles is always going to be too much. Next, I played with ellipses instead of triangles, but it’s a bit weird: Next, the drop-down on the archive is much more important than the one for the branch, which doesn’t hurt anyone if it’s not discovered. I don’t like making it inconsistent, but we could potentially do something only for the archive dropdown: Then, I came up with something that was a little more promising: The biggest issue here is mobile. It’s possible we could leave things as they are on mobile, but that’s then two different breadcrumb bars depending on the device, which is not ideal at all. All discussion on these potential fixes to this is welcome, as well as new ideas! However, until we have a path forward, I’m going to move this to be a discussion rather than an issue. |
Beta Was this translation helpful? Give feedback.
-
Please describe the bug
Related to #1974, it's not obvious that the documentation headers are pull down menus that can lead to multiple modules within a package.
Please give a clear and concise description of what went wrong.
For example, @MaxDesiatov was looking at the JavascriptKit project and didn't realize that the final element was a pull down:
I'm wondering if a disclosure triangle (or equivalent kind of UX affordance) wouldn't make sense there to provide a hint
Explain the steps needed to reproduce the bug
What was the expected behaviour?
Max didn't realize that final element was a pull-down menu, and thought documentation was missing.
Screenshots
If applicable, please add screenshots to help explain your problem.
Beta Was this translation helpful? Give feedback.
All reactions