On Tue, 18 May 2021 17:57:59 GMT, Pavel Rappo <pra...@openjdk.org> wrote:
> I wonder if we could teach JavaDoc types that model HTML that void elements > do not require end tags. Before this change, WBR required an end tag despite > being void: > https://github.com/jonathan-gibbons/jdk/blob/8a96c703771224990504cd258dd737e10d325f68/src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/formats/html/markup/HtmlTree.java#L954-L968 > > Failing that, we could have a test to catch such inconsistencies. I'm not sure I completely understand your question. There are two different distinct type systems in play. 1. There is doclint's HtmlTag, which provides declarations and properties for *checking* HTML. 2. There is the Standard Doclet's TagName, which provides declarations and properties for *writing* HTML. For better or worse, these two systems are distinct and do not fully overlap. The set of tags is different, and the properties you need when parsing/checking are somewhat different from those needed when generating HTML. And while it is easier to imagine merging them now than 6 months ago (they used to be in separate modules) it would still be a big architectural change to try and merge them, and way bigger than the current problem warrants. The output case was OK, as shown in the link you gave. It was the input side that was broken, and that is now fixed. ------------- PR: https://git.openjdk.java.net/jdk/pull/4098
