JDK-8167977 : generated javadoc bundles should use --no-frames
  • Type: Enhancement
  • Component: docs
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2016-10-13
  • Updated: 2017-04-04
  • Resolved: 2017-04-04
Related Reports
Blocks :  
JDK-8166175 - javadoc search doesn't work on local doc bundles
Blocks :  
JDK-8077046 - Can't resize JavaDoc frames
Relates :  
JDK-8173707 - Javadoc generated pages should default to no-frames view
Description
The generated javadoc documentation should use the new --no-frames option.

JDK-8077046 is a P2 report that notes that you cannot resize the frames in the latest javadoc display. Overall, the direction of the design for javadoc has been to move away from using frames entirely, and to provide a Search mechanism and improved module- and package- summary pages for browsing and navigation.

When we change the build to use --no-frames, we should reduce the priority on JDK-8077046 to P4.
Comments
According to email conversation, it was agreed that JDK-8173707 was a preferable fix.
04-04-2017
What does "not pretty" mean? Are the results any better if you change to a single docs bundle to replace the current set of over 20 bundles? One reason for getting rid of frames is that can't be resized easily, now that we have switched to HTL5-friendly <iframes> instead of HtML 4.01 Transitional <frameset> One of the justifications for why it was OK to get rid of frame was the provision of the new Search feature. With JavaScript search available, there is less need for static index lists on the left hand side.
30-11-2016
I tried --no-frames, but the result is not that pretty. Are we actually ready for this switch now?
29-11-2016