What's the bigger surprise, that by default a custom element isn't `display: block` or that it isn't `display: contents`?

[westbrook@mastodon.social]

What's the bigger surprise, that by default a custom element isn't `display: block` or that it isn't `display: contents`?

#webComponents #customElements #fridayFiguring

[ryantownsend@webperf.social]

@westbrook I really wish there was a way to target all custom elements via a single selector so I could set them all to `display: contents` in my reset.css

[noleli@mastodon.social]

@ryantownsend @westbrook :not(:defined) { display: contents; } ?

Though my intuition is that I expect them to be block

[ryantownsend@webperf.social]

@noleli @westbrook that works for undefined components, but then I still have to write a selector for every defined component.

I have many components which are purely laying on functionality rather than involved in rendering whatsoever.

[knowler@sunny.garden]

@ryantownsend @noleli @westbrook Seems like those components would benefit from the proposed custom attributes, over custom elements?

[ryantownsend@webperf.social]

@knowler @noleli @westbrook absolutely, I’m gagging for custom attributes! Be nice to reduce DOM depth too.