This is similar to #232, but for attributes.
Examples:
<meta>: http-equiv → equivalent<script>: src → source<a>: href → reference<img>: src → source<textarea>: cols → columns
Given that most HTML elements nowadays use global attributes (with most element-specific attributes being deprecated) and the few remaining element-specific attributes either share the same name (src, type, href, placeholder) or are entirely unique (http-equiv, crossorigin, autoplay), it makes sense to implement this feature at a globally scoped level, similar to the existing @Dtd(aliases=...).
This will address the primary use case (HTML), and further element-specific refinements can be introduced as separate tickets.
This is similar to #232, but for attributes.
Examples:
<meta>:http-equiv→equivalent<script>:src→source<a>:href→reference<img>:src→source<textarea>:cols→columnsGiven that most HTML elements nowadays use global attributes (with most element-specific attributes being deprecated) and the few remaining element-specific attributes either share the same name (
src,type,href,placeholder) or are entirely unique (http-equiv,crossorigin,autoplay), it makes sense to implement this feature at a globally scoped level, similar to the existing@Dtd(aliases=...).This will address the primary use case (HTML), and further element-specific refinements can be introduced as separate tickets.