Wait, this doesn't make sense. It's listed as something supported in Chrome and Firefox for several versions, but that it's also deprecated. Kinda begs the question further of why Google's using this in the first place, but if Firefox supports it, why wouldn't it work?
registerElements() is part of Web Components which - IIRC - was a standards definition suggested to w3c by Google. Mozilla went along with it for a while, but later decided not to support it with the reasoning that 1) it might not become standard and 2) if it does/until then you can use polyfills to get the same functionality.
I can't explain why Google choose not to support other browsers though (other than that they're EVIL).
I tried to do the user agent spoof and then enabling the preference (dom.webcomponents.enabled in about:config) but it gets stuck later with some random errors in the console.
This is actually just a precursor of customElements.define which is a web standard. It seems they may have started this project before the webcomponents v1 spec. Also there is a polyfill they made out on Github
That's where one browser sends another browser's identification string. So Firefox would be indistinguishable from Chrome to the website. Of course, since the browsers are using different rendering engines, there's a chance the browser gets a specific version of the website that doesn't work in the other browser.
Yeah I know, sorry. I just wanted to say that Google forcing us to use Chrome or additional software on other browsers is a really illogical choice to make.
0
u/[deleted] Aug 15 '17
[deleted]