Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)

@trusktr, I feel like maybe there is a question of whether Typescript/JSX is the cart or the horse.  To my mind, the most relevant question is not "what does Typescript/JSX support today"? but rather "could JSX/Typescript be trained to support whatever we come up with?", and we should we come up with the best solution, considering that additional question as a secondary consideration.

I was extremely excited when Typescript, I spent all night playing around with it the day it came out, but, perhaps this is an old-fashioned view, one of the things that really excited me about it is that it took an extremely subservient view to the standards at the time ("we will adopt to the standards (which we may influence a bit) even if it breaks backwards compatibility when they come out, and not the other way around").  I've not seen the same humbleness from many JSX advocates, but that's another story for another day.

Anyway, do you see any reason Typescript/JSX couldn't be trained to support autocomplete / compiling support for something like:

```JSX
<table>
  <tr [behavior-for-the-tr my-first-prop:=hello my-second-prop:=goodbye my-first-attribute=world] >
    <td></td>
  </tr>
</table>
```

???

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

Message ID: <WICG/webcomponents/issues/1029/1869667206@github.com>