Nevermind, I think I found it. https://download.java.net/java/early_access/jdk26/docs/specs/index.html
It's not exactly what I wanted, but it is good enough for me. On Mon, Nov 10, 2025, 12:26 PM David Alayachew <[email protected]> wrote: > Hello Nizar, > > Ty vm. Is there any deployed Javadocs for me to see the end results? What > you have linked to me sounds like it only does half of what I asked for, > but the Javadocs should be able to show me for sure. > > On Mon, Nov 10, 2025, 10:11 AM Nizar Benalla <[email protected]> > wrote: > >> Hello David, >> >> Thank you for the suggestion, this was fixed in JDK 26 >> https://bugs.openjdk.org/browse/JDK-8294074. >> >> Cheers, >> Nizar >> ------------------------------ >> *From:* javadoc-dev <[email protected]> on behalf of David >> Alayachew <[email protected]> >> *Sent:* Monday, November 10, 2025 11:30 AM >> *To:* [email protected] <[email protected]> >> *Subject:* Please add a tab to navigate to the tools and specs pages >> >> Hello @[email protected] <[email protected]> team, >> >> If I look up the documentation for the jar command in Java 25, I get this >> page. >> >> https://docs.oracle.com/en/java/javase/25/docs/specs/man/jar.html >> >> On the top are 3 tabs, titled as follows. >> >> * API >> * Other Specifications >> * Tool Guides >> >> If I click API, it takes me to the main Javadoc page that we know. >> However, I have no way to navigate back to that page, other than to use my >> back button. >> >> Could we add the "Other Specifications" and "Tool Guides" tabs to the >> main Javadoc page? We could put a clean vertical divider between the group >> of normal Javadoc tabs (OVERVIEW/TREE/PREVIEW/etc) and this new group. >> >> Having that ability to navigate back and forth would help discoverability >> a lot. For example, clicking on the "Tool Guides" tab shows me a whole >> bunch of features I never knew about. >> >> Ideally, this is a super low effort feature request to implement. They >> even share the same url prefix, so very very little needs to be done here. >> >> Even if we don't go about making the change, could we at least create a >> ticket for it in JBS? >> >> Thank you for your time and consideration. >> David Alayachew >> >
