attipaci opened a new issue, #1020: URL: https://github.com/apache/maven-doxia/issues/1020
### Affected version 2.0.0 ### Bug description Hi, Version 2.0.0 of `doxia-module-markdown` no longer processes anchors defined with the the deprecated `name` attribute. That is, it completely ignores: ```markdown <a name="my-anchor"></a> ``` and processes custom anchors only if these are defined with the newer `id` attribute: ```markdown <a id="my-anchor"></a> ``` While the `name` attribute has been deprecated in HTML 5, it has been treated identically to `id` before (see the [Mozilla Developer Docs](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/a)). Crucially, The [Github docs on custom anchors](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#custom-anchors) still recommend using the `name` attribute to specify custom anchors. Thus anchors in Github markdown, produced accordingly, are no longer processed as expected by Doxia. Some markdown processors may also rely on this older, now deprecated, form. As such, `doxia-module-markdown` should continue to support the deprecated `name` attribute for the `<a>` tag when defining in-page anchors to support the Github markdown specification, and older markdown documents in general. Thanks, -- Attila -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
