[foundation] semantic meaning for 'control' referenced elements in templates

[yinonov]

looking up the repo for all control members and their paired refs in templates shows incoherent pattern.

where in most cases control refs are "A reference to the internal input element", in one case (anchor) it "References the root element".

is there a convention to setting an element as control?

if it generally follows that pattern when a native form control is used, perhaps it is an anomaly in anchor? anti-pattern?

[yinonov]

I believe openui/open-ui#81 addresses this issue exactly

[chrisdholt]

I believe openui/open-ui#81 addresses this issue exactly

I think the intent here is slightly different, so I don’t see an exact application given the context, but I do agree it’s beneficial and can help lead any discussion here. From what I recall, that issue is around semantics of what constitutes what we would refer to as a “component”. We can also lean on the parts enumerated in Open UI though as we look to update those. Control in our case here is typically what we are referencing as a specific part.

[yinonov]

I believe openui/open-ui#81 addresses this issue exactly

I think the intent here is slightly different, so I don’t see an exact application given the context, but I do agree it’s beneficial and can help lead any discussion here. From what I recall, that issue is around semantics of what constitutes what we would refer to as a “component”. We can also lean on the parts enumerated in Open UI though as we look to update those. Control in our case here is typically what we are referencing as a specific part.

if it has any resemblance, it, at least, excludes References the root element from meeting control criterions, right?

[janechu]

Unfortunately @microsoft/fast-components has been deprecated for some time and we are deprecating @microsoft/fast-foundation, so this issue is obsolete.