RFR: 8335122: Reorganize internal low-level support for HTML in jdk.javadoc [v4]

[Jonathan Gibbons]

On Tue, 30 Jul 2024 18:02:32 GMT, Jonathan Gibbons <jjg at openjdk.org> wrote:

>> I'll look to upgrade these. In the original impl of DocLint, it was something of a conscious decision to avoid supporting input elements.
>> 
>> I'm surprised LINK is phrasing content: I thought it could only appear in HEAD elements. I will check.
>> 
>> Generally, moving towards HTML 5 names is a good goal, but some of that could/should be part of a DocLint cleanup. This is primarily just a merge, not an upgrade.   And, while DocLint is intended to be helpful, it is specifically for doc comments and their likely content, and not a full conformance checker.
>
> I see LINK can be phrasing content under certain conditions.
> I'll adjust the enum accordingly, but I do not think it worth updating DocLint at this time to do any additional checking.

>  I'm not sure whether marking it as INLINE content will break DocLint tests.

tools/doclint/html/OtherTagsTest.java needs to be updated

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/19916#discussion_r1697383203