Re: [WICG/webcomponents] Reference Target naming (Issue #1087)

In the case that we could "move" `role` (or similar) via a `roleDelegate` (or so), it does open the door for next level passing as I've discussed the desire for in https://github.com/WICG/webcomponents/issues/1068. It's almost like we would be drifting towards an `attributeDelegate` at some point. That's CLEARLY not what the API is at this time, however...

While, I was not quite sure how to turn `commandFor` into a usable property/attribute, I was noticing that we start with `<label for="...">` references, a couple others, and now `<button commandfor="...">` references, it seemed there might be something there. If we were "doing more 😞" then it might make sense to see a property/attribute like `attributesfor`. But, I realize that would likely derail much of the work we've done to date, which I am quite remiss to do.

I can definitely get behind a value like `referenceDelegate`! It's much like `referenceTarget`, which I'd be fine with, too, but seems like others might not be? However, language not withstanding, there would be so much gravity for the to become `delegatesReference` if only for the way it would rhyme with existing API.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1087#issuecomment-2513318519
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1087/2513318519@github.com>