Bikeshed says <{a/target}> is ambiguous, but it shouldn't be?

[domenic]

The error message is

LINE 269:91: Multiple possible 'target' element-sub refs for '['a']'.
Arbitrarily chose https://html.spec.whatwg.org/multipage/links.html#attr-hyperlink-target
To auto-select one of the following refs, insert one of these lines into a <pre class=link-defaults> block:
spec:html; type:element-attr; for:a; text:target
spec:html; type:element-attr; for:area; text:target
spec:svg2; type:element-attr; text:target
<{a/target}>

but as can be seen from the provided choices, there's only one spec for which <{a/target}> makes sense. Why make me specify it?

[tabatkins]

The actual conflict is the fact that there's an a/target in SVG as well. You can see this in the data:

╰╴bikeshed refs --text=target --spec=svg2 --type=element-attr
text:        target
displayText: target
type:        element-attr
spec:        svg2
shortname:   svg
level:       2
status:      current
url:         https://svgwg.org/svg2-draft/linking.html#AElementTargetAttribute
export:      True
normative:   True
for_:        [a]
==========
text:        target
displayText: target
type:        element-attr
spec:        svg2
shortname:   svg
level:       2
status:      snapshot
url:         https://www.w3.org/TR/SVG2/linking.html#AElementTargetAttribute
export:      True
normative:   True
for_:        [a]

I agree the options printing is a little... misleading. ^_^ It's pretty hard to figure out exactly what's optimal to display. What happens here is that exactly two refs are left - the HTML ref for [a, area] and the SVG ref for a. I end up printing the first as two options, and include the for value because it's necessary to distinguish them, and then print the second without a for value because it's not necessary to distinguish it.