Hacker News new | ask | show | jobs
by spankalee 2855 days ago
It's disappointing to see no mention of fixing the broken assumptions that lead to difficulties working with Custom Elements, like not being able to set properties from JSX: https://github.com/facebook/react/issues/11347

React is from an era where you could assume a relative static, closed-world, set of built-in DOM elements, with largely attribute and children-based configuration. Now we have open-world set of user-defined elements, and Layered APIs like <virtual-scroller>, that have rich property and method-based APIs. And it seems they will still be difficult to use from React.
2 comments
acemarke 2855 days ago
Note that Dan specifically said:

> At this stage, the project is very exploratory. We don't know for sure if all of the above things will pan out. .... If there's some area you're particularly interested in, please let me know and we'll work it out.

So, I'd keep an eye on the discussions and bring this up as something that could be worked on as part of the overall effort.

link
spankalee 2855 days ago
They're quite aware of this issue.
link
danabramov 2855 days ago
To be honest — as I was writing this a few hours ago custom elements slipped out of my mind, but it's something we'd like to fix too. It would make sense to do as part of this effort so we'll keep this in mind.
link
gb_ 2855 days ago
> Now we have open-world set of user-defined elements

Maybe this is true at Google, but I just don't see much demand for s/Web Components/Custom Elements.

link