9 ms·

Web components are not supported in many popular browsers. Until they are widely supported they are not a thing. And no, Polymer and co are not polyfills for th

by aikah 8y ago

Web components are not supported in many popular browsers. Until they are widely supported they are not a thing. And no, Polymer and co are not polyfills for them, they are their own incompatible frameworks. I agree in principle but it's up to browser vendors to implement specs, and it is always the same offender that is dragging his feet.

pjmlp 8y ago
Edge and Firefox are only missing Shadow DOM and Custom Elements, which they are already developing. On mobile Web 100% of the browsers support Web Components. https://www.webcomponents.org/ https://www.webcomponents.org/ So what are the many popular browsers you refer to? As anything else is meaningless.
- aikah 8y ago
  > Edge and Firefox are only missing Shadow DOM and Custom Elements, Your statement makes no sense whatsoever, they are "only missing" 2 of the most fundamental features of web components? that would actually help getting rid of all these incompatible UI toolkits? I don't call that supporting Web Components at all if you can't write custom elements natively. You obviously do not understand how the lack of support for custom element and shadow DOM affects Web Components adoption. Not supporting 2/3 of a spec is not being compliant with that spec, obviously.
  - ergo14 8y ago
    Edge is implementing (updated the roadmap), Firefox ships enabled WC's in closest release (it is already in the beta) I think Firefox 63 will ship in a week?. That leaves only IE11/Edge with polyfills.
    - aikah 8y ago
      > That leaves only IE11/Edge with polyfills. what polyfills are you talking about? And no, Polymer is not a polyfill for custom element. Please link me to a library that will polyfill the entire shadow DOM and Custom Element spec so that I can write the same code without polyfills on platforms that support both specs and only load the polyfills on platforms that do not.
      - pjmlp 8y ago
        https://github.com/WebComponents/webcomponentsjs https://github.com/WebComponents/webcomponentsjs Quote from the readme. " A suite of polyfills supporting the Web Components specs: Custom Elements v1: allows authors to define their own custom tags (spec, tutorial, polyfill). Shadow DOM v1: provides encapsulation by hiding DOM subtrees under shadow roots (spec, tutorial, shadydom polyfill, shadycss polyfill). "
        aikah 8y ago
        .
        ergo14 8y ago
        What do you think youtube, ing, netflix, or EA properties use? ;)
      - ergo14 8y ago
        https://github.com/webcomponents/webcomponentsjs https://github.com/webcomponents/webcomponentsjs - all frameworks use same polyfill. https://github.com/vuejs/vue-web-component-wrapper https://github.com/vuejs/vue-web-component-wrapper "You will also need the Shady DOM + Custom Elements polyfill." from Vue docs. Same polyfills are used by svelte etc.
  - pjmlp 8y ago
    Apparently you haven't read my comment as you missed "which they are already developing." and "100% support on mobile Web" part. Plus there are polyfills available for the meantime. So what other browsers are many popular?
    - aikah 8y ago
      > Apparently you haven't read my comment as you missed "which they are already developing." part. Apparently you haven't read my first comment either, since you can't tell the difference between "a spec is implemented" and "planning to implement a spec" which you obviously count as "a spec is implemented" for you or you would have refrained from making your first comment. And no, there is no polyfills for shadow DOM or Custom Element, that's a lie. Polymer is not a Polyfill for Web Components, it's his own framework. As for your question, I'm talking about browsers that do not support Custom Elements right now. Edge does not.
      - pjmlp 8y ago
        100% on mobile Web. Firefox already on beta. As for Edge it is already in development, and to be honest it doesn't matter with its insignificant market share. When Microsoft employees use only Chrome at BUILD to show Azure and .NET Core MVC features, the writing is on the wall how relevant the browser is on the market. Still you keep running away to clarify what "many browsers" means. Maybe it is my lack of native English skills, but Edge being a single browser is far away from being "many browsers", even if we include Firefox until they get out of beta, two still does not make "many browsers".
        aikah 8y ago
        > As for Edge it is already in development, and to be honest it doesn't matter with its insignificant market share. Market shares are not the same across countries, clients or even industries. That's the first mistake you are making. If I develop a product, I target whatever browser my customers use, not some world wide statistic that has very little local significance. You just don't get to ignore what goes against your point just to feel that you are winning an argument, that's childish. > 100% on mobile Web. Which is False, Firefox on Android doesn't support web components. > Firefox already on beta. Which doesn't matter if support has not shipped. "will ship" is not "has shipped". I am only interested in current support, as we speak, I was never talking about "will eventually ship" since I don't work with eventual features, obviously.
  - rb666 8y ago
    Well, I mean, it's 1 week away from release... https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/63 https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...
    - aikah 8y ago
      Well you mean it's 1 week away from release in Edge as well? Give me an ETA for Edge.
      - ergo14 8y ago
        Their roadmap was JUST updated, do probably few months.
- dschep 8y ago
  > Edge and Firefox are only missing Shadow DOM and Custom Elements, which they are already developing. > On mobile Web 100% of the browsers support Web Components. Wait. Which is it? Or are you ignoring Firefox Mobile?
  - pjmlp 8y ago
    I know that is not what HN likes to read, but iOS == Safari and Android == Chrome, and unless customer explicitly requires Firefox Mobile on the RFP, it gets ignored in acceptance testing for project delivery.
ergo14 8y ago
Yup, Polymer is "big" dependency, but with things like svelte, litelement or stencil you can build web components which have little overhead. Also polyfills are separate thing from polymer - they are reused by ALL other frameworks including vuejs for example, so I'm not sure what you meant by that comment.
- deleted 8y ago
  [deleted]

by aikah 8y ago

pjmlp 8y ago

Edge and Firefox are only missing Shadow DOM and Custom Elements, which they are already developing. On mobile Web 100% of the browsers support Web Components. https://www.webcomponents.org/ https://www.webcomponents.org/ So what are the many popular browsers you refer to? As anything else is meaningless.

aikah 8y ago
> Edge and Firefox are only missing Shadow DOM and Custom Elements, Your statement makes no sense whatsoever, they are "only missing" 2 of the most fundamental features of web components? that would actually help getting rid of all these incompatible UI toolkits? I don't call that supporting Web Components at all if you can't write custom elements natively. You obviously do not understand how the lack of support for custom element and shadow DOM affects Web Components adoption. Not supporting 2/3 of a spec is not being compliant with that spec, obviously.
- ergo14 8y ago
  Edge is implementing (updated the roadmap), Firefox ships enabled WC's in closest release (it is already in the beta) I think Firefox 63 will ship in a week?. That leaves only IE11/Edge with polyfills.
  - aikah 8y ago
    > That leaves only IE11/Edge with polyfills. what polyfills are you talking about? And no, Polymer is not a polyfill for custom element. Please link me to a library that will polyfill the entire shadow DOM and Custom Element spec so that I can write the same code without polyfills on platforms that support both specs and only load the polyfills on platforms that do not.
    - pjmlp 8y ago
      https://github.com/WebComponents/webcomponentsjs https://github.com/WebComponents/webcomponentsjs Quote from the readme. " A suite of polyfills supporting the Web Components specs: Custom Elements v1: allows authors to define their own custom tags (spec, tutorial, polyfill). Shadow DOM v1: provides encapsulation by hiding DOM subtrees under shadow roots (spec, tutorial, shadydom polyfill, shadycss polyfill). "
      - aikah 8y ago
        .
        ergo14 8y ago
        What do you think youtube, ing, netflix, or EA properties use? ;)
    - ergo14 8y ago
      https://github.com/webcomponents/webcomponentsjs https://github.com/webcomponents/webcomponentsjs - all frameworks use same polyfill. https://github.com/vuejs/vue-web-component-wrapper https://github.com/vuejs/vue-web-component-wrapper "You will also need the Shady DOM + Custom Elements polyfill." from Vue docs. Same polyfills are used by svelte etc.
- pjmlp 8y ago
  Apparently you haven't read my comment as you missed "which they are already developing." and "100% support on mobile Web" part. Plus there are polyfills available for the meantime. So what other browsers are many popular?
  - aikah 8y ago
    > Apparently you haven't read my comment as you missed "which they are already developing." part. Apparently you haven't read my first comment either, since you can't tell the difference between "a spec is implemented" and "planning to implement a spec" which you obviously count as "a spec is implemented" for you or you would have refrained from making your first comment. And no, there is no polyfills for shadow DOM or Custom Element, that's a lie. Polymer is not a Polyfill for Web Components, it's his own framework. As for your question, I'm talking about browsers that do not support Custom Elements right now. Edge does not.
    - pjmlp 8y ago
      100% on mobile Web. Firefox already on beta. As for Edge it is already in development, and to be honest it doesn't matter with its insignificant market share. When Microsoft employees use only Chrome at BUILD to show Azure and .NET Core MVC features, the writing is on the wall how relevant the browser is on the market. Still you keep running away to clarify what "many browsers" means. Maybe it is my lack of native English skills, but Edge being a single browser is far away from being "many browsers", even if we include Firefox until they get out of beta, two still does not make "many browsers".
      - aikah 8y ago
        > As for Edge it is already in development, and to be honest it doesn't matter with its insignificant market share. Market shares are not the same across countries, clients or even industries. That's the first mistake you are making. If I develop a product, I target whatever browser my customers use, not some world wide statistic that has very little local significance. You just don't get to ignore what goes against your point just to feel that you are winning an argument, that's childish. > 100% on mobile Web. Which is False, Firefox on Android doesn't support web components. > Firefox already on beta. Which doesn't matter if support has not shipped. "will ship" is not "has shipped". I am only interested in current support, as we speak, I was never talking about "will eventually ship" since I don't work with eventual features, obviously.
- rb666 8y ago
  Well, I mean, it's 1 week away from release... https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/63 https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...
  - aikah 8y ago
    Well you mean it's 1 week away from release in Edge as well? Give me an ETA for Edge.
    - ergo14 8y ago
      Their roadmap was JUST updated, do probably few months.
dschep 8y ago
> Edge and Firefox are only missing Shadow DOM and Custom Elements, which they are already developing. > On mobile Web 100% of the browsers support Web Components. Wait. Which is it? Or are you ignoring Firefox Mobile?
- pjmlp 8y ago
  I know that is not what HN likes to read, but iOS == Safari and Android == Chrome, and unless customer explicitly requires Firefox Mobile on the RFP, it gets ignored in acceptance testing for project delivery.

ergo14 8y ago

Yup, Polymer is "big" dependency, but with things like svelte, litelement or stencil you can build web components which have little overhead. Also polyfills are separate thing from polymer - they are reused by ALL other frameworks including vuejs for example, so I'm not sure what you meant by that comment.

deleted 8y ago
[deleted]