Hi Guys,
We have some awesome elements we want to introduce in our upcoming webapp. The problem is that they arent compatible with chrome version 30 which is the current version running on clover devices. Can you give me some insight as to when, if ever, you plan on updating the version of chrome used on the device?
Clover Station uses a custom browser based on Mozilla Firefox known as Clover Browser. In the past, Clover Station used Android Browser, but it has been removed and replaced.
Thanks Brian, this is absolutely correct in regards to the Clover Browser app. However, what I'm referring to is the WebView component which, at least according to my understanding, is how we should allow access to web-based apps on clover devices. It's the WebView which is running Chrome 30. So, with that in mind could you answer --
(1) Is using WebView the suggested way for clover developers to embed web content into their apps? Or is there a way to embed using the Clover Browser? (2) Are there plans to update the WebView component? (Which is 23 versions out of date as of today)
Yes, WebView is the recommended way to integrate web content. No, there are no plans to update the web view. Moving to a new web view is risky considering the security concerns so it'd help top understand what's not supported or not working with the current version.
So the tools that we were trying to use were really just basic web design stuff. Flexboxes and css, but Chrome 30 is from 2013, so it doesn't implement those things properly, and thus wholly excludes Clover devs from using things like Bootstrap 4 or Polymer in our interfaces -- which is a loss for the merchants since they benefit from having those nice UIs we could otherwise build.
The security point is aptly put, although one might argue the security risks are greater in maintaining the 2013 version of Chrome.
If you check out https://en.wikipedia.org/wiki/GoogleChromeversion_history you can see that nearly every version since 30 has included performance & security fixes (many of which are presumably known and exploitable).
Clover may particularly be interested in updates from late 2014 (version 39 & 40) where SSLv3 support was removed. The Clover API already prohibits SLSv3 connections because they're not secure... yet we'd pass customer infromation through a webview and since it's Chrome 30 even if we force HTTPS we can't prevent that same information being transmitted over SSLv3. So bottom line is, until the Chrome version is allowed to be updated with the latest bug fixes we cannot guarantee safety of Clover customers' and merchants' data using any web app.
Thanks for the info Brian. Are there any plans to update it?
3 People are following this question.
