4 ms·

Yeah, you're right: it appears it is just a skin: https://developers.google.com/chrome/mobile/docs/faq https://developers.google.com/chrome/mobile/docs/faq Per

Yeah, you're right: it appears it is just a skin: https://developers.google.com/chrome/mobile/docs/faq https://developers.google.com/chrome/mobile/docs/faq Perhaps the idea was to get something out there for presence and then create a full rendering engine later? But then again, both Chrome and Safari are WebKit and Firefox is Gecko so I'm not sure how that changes things.

georgemcbay 14y ago
The core issue is actually JavaScript as I mentioned in another post. I doubt Google thinks this will ever change and they assume they'll never be able to deliver full Chrome on iOS. They provide the Chrome they do provide because one of the nice features of Chrome is universal syncing (of bookmarks, etc) between all your Chrome-running devices that you are signed into. While Chrome on iOS isn't really Chrome, it does sync in to this so that your bookmarks, etc, work there just like on any real Chrome browser.
- rohitnair 14y ago
  Firefox had a similar offering called Firefox Home on iOS which would sync bookmarks, history and even open tabs. It worked/works really well and I still use it. Mozilla, however, recently retired the app and made the source available on github[1]. The fact that Firefox currently has virtually no support on iOS is really frustrating for Firefox users in the Apple ecosystem. [1] - https://blog.mozilla.org/services/2012/08/31/retiring-firefox-home/ https://blog.mozilla.org/services/2012/08/31/retiring-firefo...