This app was mentioned in 11 comments, with an average of 1.91 upvotes
This commit shows the old logo that it's replacing: https://github.com/mozilla/gecko-dev/commit/0e4a2a4a5234c21a023df4d5d9e4f17e4e0382c1 , which was a version of the Firefox logo with the fox removed and the visible side of the "planet" shown at nighttime. I'm guessing that the new logo, which is just a pallet-swap of the refreshed Firefox logo, is blue both to provide continuity with the old logo and to be a rough inverse of the color scheme of stable Firefox. Note that this sort pf pallet-swap is also what Chrome does with its yellow Canary logo: https://play.google.com/store/apps/details?id=com.chrome.canary&hl=en
> the feature is already live in Chrome Canary and is also available in WebView, just head to chrome://flags to turn it on.
That's not what live means.
Chrome Canary is more up to date if you don't mind bleeding edge. I think you need to install it via the web store to get it on the device: https://play.google.com/store/apps/details?id=com.chrome.canary
FYI, you can try this out today. I've only found 1 app that it works with so far - Flipboard.
How to:
Install Chrome canary https://play.google.com/store/apps/details?id=com.chrome.canary
Open Chrome canary, and go to URL chrome://flags
Find the setting #enable-improved-a2hs
Set it to Enabled
Relaunch Chrome Canary when prompted.
Go to Flipboard.com
Press "Add shortcut" in the menu
The Flipboard website will then prompt you to install like any other app
Have the pixelbook, everything runs great for me. I suspect that the cheaper chromebook models run at weird resolutions that might have other issues. KB+M/Controller both work fine on the Pixelbook.
You can try downloading canary https://play.google.com/store/apps/details?id=com.chrome.canary and see if being on the bleeding edge version yields better results.
You should also look at disabling mouse acceleration in ChromeOS settings ,just search for it, if it is on (or turn it on if it is off).
You can also try changing your DNS to Google and see if that routing helps, it honestly shouldn't matter but you might have a shitty DNS from your ISP.
Try the Canary release channel
They (supposedly) fixed it somewhere on the 79.x tree. Canary is on the 80.x tree, but should be the first channel to receive fixes. You could also try the Chrome-Dev (79) as well.
You could probably just install canary too. Then run both of them.
https://play.google.com/store/apps/details?id=com.chrome.canary&hl=en_US
...Canary?
Chrome Canary version: https://play.google.com/store/apps/details?id=com.chrome.canary is now at version 80 so should work.