javadoc should put a lot of blank lines at the end of the generated class pages,
using <br> This is needed because browsers treat links to the bottom of the
page to not show blank lines past the end of the page. So when I follow a "see
also" link to a method near the end of the class documentation, I don't actually
get taken to that method, but only to the bottom of the file, where I have to then
find the method among the several on my screen. On methods farthur up in the
file, this doesn't happen -- I get the actual method at the top of my browser
window.
40 or so <br>'s at the end of the page will make the behavior consistent at a very
low overhead (160 bytes).
using <br> This is needed because browsers treat links to the bottom of the
page to not show blank lines past the end of the page. So when I follow a "see
also" link to a method near the end of the class documentation, I don't actually
get taken to that method, but only to the bottom of the file, where I have to then
find the method among the several on my screen. On methods farthur up in the
file, this doesn't happen -- I get the actual method at the top of my browser
window.
40 or so <br>'s at the end of the page will make the behavior consistent at a very
low overhead (160 bytes).