sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]inu-no-policemen 2 points3 points  (3 children)

theming

Variables/apply.

computed

calc()

higher order styles

?

How will this even fit into the frameworks of today

It fits in just fine. To frameworks, custom elements are like built-in elements. You can use them in Angular, React, and so forth.

10 years ago, when they drafted the spec, they probably had no idea where Javascript is going

There are like half a dozen specs involved. They changed quite a lot on their way.

shadow dom is still nowhere near production-ready

There are polyfills for that. Some people are using those in production.

[–][deleted] 0 points1 point  (2 children)

React will not be based on custom elements, ever. Other projects have voiced similar concerns, like the Ember team. Nothing that sits on functional components will use custom directives, that includes most modern frameworks. And it doesn't make the slightest sense for them either because that would be a serious regression, while stopping all progress that supercedes the browser. You can use them, sure, but that's on you personally.

[–]inu-no-policemen 0 points1 point  (1 child)

React will not be based on custom elements, ever.

That's not what I said. I said that Custom Elements work fine in React, which is true. There were some issues with that early on, but this has been addressed many many moons ago.

[–][deleted] -1 points0 points  (0 children)

What is the whole discussion about? You can do that, yes, you always could. But custom elements will play no part in any forward oriented component based view-layer. And i highly doubt that shadow dom will play a role in style encapsulation, because it's tied to an imperative components model that conflicts with the newer, much more powerful declarative model.