(This bug is filed in the RT project and the Control component so that it will show up in the UI Controls queries.)
Javafxdoc output mangles relative links from within package docs. The issue concerns processing of the @link tag. A tag that includes the fully qualified package name, such as {@link javafx.scene.layout.Container Container} works just fine. A link to a class within the same package, such as {@link ListView} from within the javafx.scene.control package.html file, results in a malformatted link. The link should look something like ".../docs/api/javafx.scene.control/ListView.html". Instead, the package name is missing, the first three letters of the class name are missing, and the .html suffix is missing. The result is a link like ".../docs/api/tView" which doesn't work.
This is probably an error in the XSLT post-processing step of javafxdoc.
Javafxdoc output mangles relative links from within package docs. The issue concerns processing of the @link tag. A tag that includes the fully qualified package name, such as {@link javafx.scene.layout.Container Container} works just fine. A link to a class within the same package, such as {@link ListView} from within the javafx.scene.control package.html file, results in a malformatted link. The link should look something like ".../docs/api/javafx.scene.control/ListView.html". Instead, the package name is missing, the first three letters of the class name are missing, and the .html suffix is missing. The result is a link like ".../docs/api/tView" which doesn't work.
This is probably an error in the XSLT post-processing step of javafxdoc.