non-chrome

No (non-chrome) distro currently works out of the box on the c720 (at least among the x64 variants).

> the ban on non-Chrome browsers accessing Hangouts What do you mean by this?

Any ETA on when your site will be fixed for non-Chrome users?

This means that non-Chrome password managers have many constraints that Chrome does not.

Chrome isn't trying to not let other (non-chrome) processes read info.

Also the non-Chrome version of Android Gingerbread's browser lacks SNI support.

Currently, some/all non-Chrome browsers won't do the extra prefetches.

It was the reason cited for blocking non-Chrome browsers—i.e.

Continuing with our example of BoA, this doesn't matter because they have not opted in [0] to that and in any case that won't apply to non-chrome requests.

Can someone explain this for a non-Chrome user?

Inbox doesn't work on non-chrome browsers.

A few people downloaded non-chrome store extensions, but most of them downloaded the ones that were left in the store - the malware extensions that promised to download youtube but didn't.

So if you're ever trying to debug promises in a non-Chrome browser, you may find my "insane" advice pretty helpful.

Regarding the author's comment, "The problem is that the Web is now optimized for Chrome users and that means alternatives often provide a terrible experience." What are some examples of sites that provide a terrible experience to non-Chrome users?

Chrome (dunno if enabled by default and/or in stable) contains a Dart VM, so you "only" need to transpile into JS for non-Chrome.

There's a big difference between "provided a degraded experience in non-Chrome browsers" and "actively blocking non-Chrome browsers by means more invasive than UA checking" Remember, there isn't any kind of really legitimate API for 100% determining which browser you're running in.