Doug Parker 🕸️ on Nostr: If the element is rendered client side, then yes I agree it should be render ...
If the element is rendered client side, then yes I agree it should be render blocking. `<some-comp></some-comp>` isn't meaningful to the user until it is rendered.
However from a strictly progressive enhancement perspective, I'd argue that the element should either:
1. Be server-side rendered such that it doesn't need to block on the CE definition.
2. Not be added to the page until the resources to render it have been loaded (you're breaking rendering for other things on the page).
You could do 2. with a `<script async>` which adds the element after defining it though this can be unergonomic.
Maybe improving the tooling and capabilities on that side might be more in line with PE ideals and avoid render blocking resources?
However from a strictly progressive enhancement perspective, I'd argue that the element should either:
1. Be server-side rendered such that it doesn't need to block on the CE definition.
2. Not be added to the page until the resources to render it have been loaded (you're breaking rendering for other things on the page).
You could do 2. with a `<script async>` which adds the element after defining it though this can be unergonomic.
Maybe improving the tooling and capabilities on that side might be more in line with PE ideals and avoid render blocking resources?