News for hackers. Stuff that matters.
Re:Open-sourcing Chrome on iOS by DonHopkins on Tuesday January 31, 2017 @02:43PM (#13534460)
How much is there even left for Chrome to do, once you are building on top of a WKWebView? Seems like Chrome would be a very thin layer on top of it, with WKWebView doing most of the work, and Chrome just implementing a thin layer of user interface widgetry on top of that (next and back button, url bar, etc). Sounds to me like it's just a branded "white label" version of Apple's standard Safari browser.
Re:Open-sourcing Chrome on iOS by jmascart on Tuesday January 31, 2017 @03:00PM (#13534631)
> How much is there even left for Chrome to do

Looking at https://chromium.googlesource.com/chromium/src.git/+/master/... there is:

autocomplete, autofill, content settings, content suggestions, crash reporting, desktop promotion, device sharing, dom distiller, favicon, find in page, first run, geolocation, history, infobars, metrics, open from clipboard, passwords, payments, physical web, prefs, reading list, search engines, share extension, signin, ssl, suggestions, sync, translate, voice

Re:Open-sourcing Chrome on iOS by mmphosis on Tuesday January 31, 2017 @03:28PM (#13534881)
Many of the things that I want removed from Chromium / Chrome.
Re:Open-sourcing Chrome on iOS by eriknstr on Tuesday January 31, 2017 @03:39PM (#13534976)
Well now that it's open source you could in theory remove the things you don't want and keep only the good parts. In practice it's not realistic for a single person to do it and even if it was you'd still have to maintain it.
Re:Open-sourcing Chrome on iOS by hendersoon on Tuesday January 31, 2017 @02:50PM (#13534535)
It is indeed.

Chrome on iOS has some neat UI innovations, though-- when you drag down on a page you see three icons; a + sign for a new tab, a refresh icon, and an X to close the current tab. So you can drag straight down to refresh, down then left to add a new tab, etc. I really miss that in safari.

It also syncs history, logins, open tabs, etc, with desktop Chrome.

Re:Open-sourcing Chrome on iOS by mdonahoe on Tuesday January 31, 2017 @03:18PM (#13534794)
I am glad they abandoned swipe-to-switch-tabs for swipe-to-go-back like Safari uses. Much more useful IMO
Re:Open-sourcing Chrome on iOS by curt15 on Tuesday January 31, 2017 @03:35PM (#13534933)
I've always wondered why the Android version does not have swipe to go back.
Re:Open-sourcing Chrome on iOS by eggnet on Tuesday January 31, 2017 @03:46PM (#13535034)
Android has a system level back button.
Re:Open-sourcing Chrome on iOS by StRoy on Wednesday February 01, 2017 @04:05PM (#13545171)
Which is not as convenient to use on larger phones, one handed, compared to a gesture that works anywhere on the web page. I have a Honor 8 and while overall I'm very satisfied with the apps, speediness of the phone, the lack of gestures in most Android apps compared to iOS gets old very fast, even more so because 99% of all the good android handsets on the market are much bigger than the iPhone 5s I had before.

Saying you can press the back button located on the bottom left side of the screen really doesn't cut it.

Re:Open-sourcing Chrome on iOS by NTripleOne on Thursday February 02, 2017 @09:52AM (#13550871)
However will you overcome such a grievous inconvenience?!
Re:Open-sourcing Chrome on iOS by javier2 on Tuesday January 31, 2017 @05:29PM (#13535940)
These three shortcuts are the reason I never use Safari on my iphone.
Re:Open-sourcing Chrome on iOS by BHSPitMonkey on Tuesday January 31, 2017 @02:50PM (#13534536)
Bookmark/tab sync, for one. Desktop Chrome users can access tabs/history originating from the iOS client.
Re:Open-sourcing Chrome on iOS by X-Istence on Tuesday January 31, 2017 @02:59PM (#13534623)
Safari bookmarks/tabs sync across iOS/macOS as well. You can also access tabs/history originating from the iOS client.
Re:Open-sourcing Chrome on iOS by el_benhameen on Tuesday January 31, 2017 @03:05PM (#13534693)
I'm in the middle of a trial switch to Safari so that I can utilize this, but man, Safari on the desktop is such a pain compared to Chrome that I think I'm going to have to sacrifice the feature.