-
Task
-
Resolution: Duplicate
-
P3
-
21
-
generic
-
generic
Currently, javadoc-generated API documentation adapts to large screens simply by expanding page content to the available screen space. This is aesthetically questionable and results in usability problems: Running text becomes hard to read due to very long lines, and links and other page elements become difficult to reach as they are scattered over a large area.
Similar to the work done for small screens, we should make the page layout responsive to large screens. A simple approach would be to limit the space used by individual page elements. A more sophisticated solution would be to switch to a different layout on large screen, possibly using additional columns or grid cells, and using the available space for additional content or navigation features.
Similar to the work done for small screens, we should make the page layout responsive to large screens. A simple approach would be to limit the space used by individual page elements. A more sophisticated solution would be to switch to a different layout on large screen, possibly using additional columns or grid cells, and using the available space for additional content or navigation features.
- duplicates
-
JDK-8320458 Improve structural navigation in API documentation
- Resolved
- is blocked by
-
JDK-8308659 Use CSS scroll-margin instead of flexbox layout in API documentation
- Resolved