Changes to look and feel of javadoc generated API pages in JDK 8

[Mike Duigou]

This looks like a nice refinement.

Some immediate bits of feedback:

- The size of <pre> and {@code } elements differs. (14.4px vs 14px). This is also a problem with the existing templates.

- Why px for most but not all measurements? I would personally prefer to see em units used to tie sizing of elements to user's preferences. (http://www.w3.org/WAI/GL/css2em.htm) At minimum, use either all px or all em. To see badness, drastically adjust the size of your default font. E A few UI elements will now look weird (Trademarks, legal text, height of nav bars, etc.

- All of the text could be somewhat higher contrast. #666666 is too low for body copy. Perhaps it's just the Deja Vu font. I keep thinking the text is transparent.

- Verdana would be preferable to Arial as a fallback for headings.

Mike


On Nov 6 2013, at 13:43 , Bhavesh Patel <bhavesh.x.patel at oracle.com> wrote:

> Hi All,
>       Based on the feedback received on the new UI implementation in JDK 7 javadoc, we have made some minor changes to look and feel of the API pages generated by javadoc in JDK 8. The JDK API documentation pages will be using DejaVu font. A sample build, using the DejaVu fonts, can be found at http://cr.openjdk.java.net/~bpatel/docs/dejaVu/api/. Non-JDK API documentation pages that are generated by the user of the javadoc tool will be using non-DejaVu fonts as specified in the stylesheet.css file. A sample build can be found at http://cr.openjdk.java.net/~bpatel/docs/api/.
>       Please provide any feedback, that you might have, on these new look and feel changes in both the versions.
> 
> Regards,
> Bhavesh.