JDK-4131628 : stddoclet: Next/Prev Class don't iterate through all interfaces AND classes
  • Type: Bug
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 1.2.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_2.5
  • CPU: sparc
  • Submitted: 1998-04-22
  • Updated: 2014-05-05
  • Resolved: 2003-11-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b28Fixed
Description
There's a subtle user-interface issue with Next Class / Prev Class that
needs correcting. 

Clicking "Next Class" should go through all the interfaces in the current 
package alphabetically, and then all the classes alphabetically without
any separation (and without wrapping around to the start).  
"Prev Class" should go in the reverse direction.

As has been true since 1.0, Next/Prev iterates through
classes and interfaces separately.  In other words, you cannot
iterate continuously through classes and interfaces -- only 
classes or interfaces.  This is confusing.  Most people
would want and expect to be able to iterate through the entire
package. 

To be more specific, when you are at an interface page (not a class page) 
and click "Next", it takes you to the next alphabetic interface in that 
package.  When you hit the last interface you can't get to the classes.
To get to the classes, you have to go to the package summary and click
on a class, then "Next" takes you through the classes.

This is a bad design, because it's so difficult to get
from interfaces to classes.  Someone iterating through the classes 
might not realize that the interfaces were not included in that iteration.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger tiger-beta FIXED IN: tiger tiger-beta INTEGRATED IN: tiger-b28 tiger-beta
14-06-2004

PUBLIC COMMENTS Fixed. ###@###.### 2003-10-11
11-10-2003

EVALUATION Not a high priority, because these links are seldom used, but useful to do someday. doug.kramer@Eng 2001-03-01 As described, this would correspond to how the interfaces and then classes appear in the lower left frame (when a package is selected in the upper right frame). In this case, Enums, Annotations, Errors and Exceptions should also be grouped in the order as shown in that frame. Or should the classes and interfaces all be mixed together in a single ordered list A-Z? This would make more sense when the frame is not showing. ###@###.### 2003-09-24 Fixed. ###@###.### 2003-10-11
24-09-2003