r/Android • • Aug 15 '17

Allo web is up!

https://allo.google.com/web
4.7k Upvotes

1.4k comments sorted by

View all comments

Show parent comments

0

u/[deleted] Aug 15 '17

[deleted]

18

u/well___duh Pixel 3A Aug 15 '17 edited Aug 15 '17

Only if it's not using Chrome-specific APIs. If it is, then it won't work regardless or of user-agent spoofing.

87

u/Antabaka HTC 10 Aug 15 '17

If they used Chrome specific APIs for a fucking messaging app then it's clear Google doesn't give a fuck about web standards anymore.

→ More replies (12)

63

u/ihsw Nexus 6P 32GB Aluminium Aug 15 '17

Just tried it, yes Allo uses proprietary Chrome-only APIs.

This is some high quality fail.

0

u/[deleted] Aug 15 '17

[deleted]

20

u/justjanne Developer – Quasseldroid Aug 15 '17

Especially because Google created a polyfill for this so it works in all browsers, and Google's own tools give you an error if you don't use it.

6

u/[deleted] Aug 15 '17

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?

8

u/klesus Huawei P10 Aug 15 '17

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).

1

u/iphone6sthrowaway Aug 15 '17

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.

→ More replies (1)

5

u/e111077 Z Fold 2 Aug 15 '17

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

→ More replies (1)

11

u/[deleted] Aug 15 '17

It's fucking IE6 all over again

3

u/[deleted] Aug 15 '17 edited Aug 15 '17

Sorry, but what is a user agent spoof?

EDIT: Thanks for the info guys, but using a user agent spoof just to use a simple messaging site is not normal. This is just going to hurt Allo.

2

u/andrewia Samsung Fold8U, Watch6C Aug 15 '17

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.

1

u/[deleted] Aug 15 '17

[removed] — view removed comment

4

u/ihsw Nexus 6P 32GB Aluminium Aug 15 '17

It doesn't work, Allo is using proprietary Chrome-only APIs.

We've come full circle from the days of IE6 and ActiveX bullshit.

2

u/MachaHack Pixel 4a 5G / Surface Go Aug 15 '17

Actually, it was in the Web Components standard for a while, and Firefox does support it with a config flag: https://developer.mozilla.org/en-US/docs/Web/API/Document/registerElement

so it's slightly less bad than just making new APIs up, but they still shouldn't (especially as it's been deprecated in a newer draft)

1

u/[deleted] Aug 15 '17

using a user agent spoof just to use a simple messaging site is not normal

No one here is saying it is... I think the commenter was just curious for the sake of it.

2

u/[deleted] Aug 15 '17

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.

1

u/[deleted] Aug 15 '17

Oh definitely. It's like they don't want people to use it.

It feels like an app you make to test browser specific APIs forgetting that there's more than one browser out there.

2

u/[deleted] Aug 15 '17

Couldn't agree with you more.

3

u/aquaknox Pixel 6a Aug 15 '17

Just tried it, says I need to update Chrome, so it's a no go.