2 ms·
> Webcomponents once Chrome 77 drops and Firefox matches parity will finally be production worthy, and they're actually quite easy to build. What's changing in
by majewsky 7y ago
> Webcomponents once Chrome 77 drops and Firefox matches parity will finally be production worthy, and they're actually quite easy to build.
What's changing in Chrome 77? A caniuse search for "web components" does not turn up anything that's not old news.
- jjcm 7y agoForm registration for webcomponents is coming. Personally when trying to create a component system it's been the number one blocker I've had. Your work arounds were not great - either you'd have to mirror an input in the lightdom (not good if you're using a library that strictly enforces a vdom), or you have to use a forked form component (not good as few people will know to use it and will wonder why the x-input isn't sending its data to the form). Once form registration is in place you'll be able to create component libraries that should truly work no matter the environment or libraries being used alongside them (as long as you have an up to date browser).
- triangleman 7y agoCan you link me to a page describing this new functionality in action?
- jjcm 7y agoSure, here's the API proposal that's been approved: https://docs.google.com/document/d/1JO8puctCSpW-ZYGU8lF-h4FWRIDQNDVexzHoOQ2iQmY/ https://docs.google.com/document/d/1JO8puctCSpW-ZYGU8lF-h4FW... As well as the implementation status in chromium: https://www.chromestatus.com/features/4708990554472448 https://www.chromestatus.com/features/4708990554472448