Export attributes common to form controls (e.g. autocomplete) and their values (e.g. autocomplete=one-time-code)

[hober]

I'd like to autolink to the autocomplete attribute's one-time-code value from a Bikeshed document with <{element/attribute/attribute value}> syntax, but I've run into two problems:

• The spec doesn't appear to export it.
• re: the Bikeshed syntax, what should element be for attributes common to form controls?

[annevk]

cc @tabatkins

[tabatkins]

re: the Bikeshed syntax, what should element be for attributes common to form controls?

Ultimately up to the spec; there's no good generalized answer.

I suggest maybe form-control?

[annevk]

That sounds reasonable.

We should probably document somewhere what we use so we can make consistent choices here.

[tabatkins]

Yup, happy to update Bikeshed docs with this (and whatever we decide for global attributes)

[annevk]

I had a look at our data-dfn-for usage for element-related things:

• htmlsvg-global: nonce content attribute (seems okay, but might soon include Math so maybe not?)
• HTMLOrSVGElement: [[CryptographicNonce]] internal slot, but "parser-inserted" uses script
• HTMLOrSVGElement: nonce IDL attribute (seems okay)
• node: language (this should be Node I think)
• script: used for concept-script as well as the script element. Might be okay due to different types? Not sure.

There isn't much of it at all.

[tabatkins]

Might be okay due to different types? Not sure.

Yes, the for values are just opaque strings as far as Bikeshed is concerned, and are scoped to the dfn type, so you can reuse for values between different types without any fear of clashing.

nonce content attribute (seems okay, but might soon include Math so maybe not?)

Yeah, I'd probably make that more generic. Either global or markup-global or something?

[two uses of HTMLOrSVGElement]

These are correct, that's the interface they're attached to.

[domenic]

I think the correct value for these is the list of applicable elements in a comma-separated list. For example,

<dfn element-attr for="button,fieldset,input,output,select,textarea,form-associated-ce"><code>name</code></dfn>

<dfn element-attr for="button,input,optgroup,option,select,textarea,form-associated-ce"><code>disabled</code></dfn>

...

[hober]

Any progress on this?