4 ms·

That's probably because custom elements aren't supported in Firefox yet, unless you set "dom.webcomponents.enabled" and "dom.webcomponents.customelements.enable

That's probably because custom elements aren't supported in Firefox yet, unless you set "dom.webcomponents.enabled" and "dom.webcomponents.customelements.enable" to true. It's supposed to be fully enabled in Firefox 60/61 according to MDN [0]. [0]: https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements https://developer.mozilla.org/en-US/docs/Web/Web_Components/...

the8472 9y ago
Best viewed with Chrome Explorer™ 5.0, Optimized for 1024x786 truecolor screens.
ehsankia 9y ago
Sure, but should they not be either using polyfills, or not use code that is only supported by one browser? I understand how a project like Allo Web would want to use latest streaming api tech, but a documentation/product launch page doesn't need crazy new web tech.
- shdh 9y ago
  They should be using the polyfills, but looks like someone missed the mark and forgot to add them.
  - kuschku 9y ago
    They didn't even test on anything other than Chrome, because they don't care. That's the problem. Not that it was missed, but that they didn't even test in Firefox.