On Tue, 12 Dec 2023 21:38:33 GMT, Joe Darcy <da...@openjdk.org> wrote:
> Should this issue have a CSR for the behavioral change? My understanding of the issue is that the lookup of explicit-class member references in enclosing classes was an unintended consequence of doing the same for classless references from within nested classes. So I consider this a bug fix, not a feature change (even though it unfortunately changes javadoc to become stricter in what it accepts). Actually, the feature of extending member reference lookup to enclosing classes is not specified in the taglet spec, which only says this: > When the reference is to a member of the same class as that containing the > documentation comment, all parts of the reference up to and including the # > may be omitted, although the '#' may be retained for clarity. This could be extended to include enclosing classes, but this is existing behaviour, not changed by this issue. ------------- PR Comment: https://git.openjdk.org/jdk/pull/17069#issuecomment-1853676675
