3 ms·
Are standard web components on the roadmap for this? They are expected to have wide browser support this year, so it’s a good time to start using them as a foun
by SimeVidas 10y ago
Are standard web components on the roadmap for this? They are expected to have wide browser support this year, so it’s a good time to start using them as a foundation (there is a polyfill for non-supporting browsers). For the uninformed, they will remove all the overhead of having to manually manage the style sheets and CSS classes; instead, the developer just inserts custom elements (e.g.<frend-accordion>) and everything is taken care of automatically.
- codecamper 10y agoDo you mean Polymer for the polyfill?
- spankalee 10y agoPolymer is not a polyfill, it uses the webcomponentsjs polyfills: https://github.com/webcomponents/webcomponentsjs https://github.com/webcomponents/webcomponentsjs
- adamduncan 10y agoGood question, Šime. We'd be open to a move to web components in the future. At their core, it seemed beneficial to keep the inner workings as visible as possible - transparent examples of each pattern based on specs. Although there is a maintenance trade-off, definitely. Could you see a web component version living alongside the standard implementation?
- spankalee 10y agoWhy would a web component not be a standard implementation? Web components are literally the standard way to create new HTML tags, and render and style the internals in an encapsulated way.