Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

I realize I'm very late to the party here, but given that this thread is nearly old enough to go to elementary school, I was wondering if any progress has been made on the subject of exposing native built-in functionality to web component authors? Either through built-in subclassing, or mixins, or compositional primitives like @rniwa was talking about earlier in this thread...? Is there another issue with more up-to-date discussion?

I would love to be able to migrate away from the heavy-handed JavaScript frameworks I'm currently relying on, but this is a huge deal-breaker. A big reason I was excited about web components to begin with is because I thought it would allow for creating things like custom form controls and UI widgets _without_ going through the pain of manually implementing the ARIA specs. But if I need to do all that anyway, it's a heck of a lot easier to manage that complexity through a higher-level framework like Angular than through the web components API, even with a sugary layer like lit-element / fast-element / Stencil / whatever on top of it.

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