Comment # 4 on bug 965738 from Raymond Wooninck

(In reply to George Anchev from comment #2)
> > Maybe other distributions are patching chromium, but on openSUSE I am trying
> > to stay as close as possible to the official tarball. Of course it will
> > never be equal to chrome, but it comes very close to it.
> 
> Could you please explain why? When talking about stable versions - isn't it
> supposed that Chromium and Chrome are the same thing, just the former one
> being FOSS and not sending tracking info to Google? (at least this is what I
> read in articles around the web)

Well, I am not sure about the tracking info, etc. However inside the code
Google made the split between chromium and chrome branding. Certain features
are only active on the chrome branding. If you take a real plain chromium build
then you will notice that widevine is not active and only recently the pdf
library became also available for Chromium (before it was only available with
Chrome). So Chromium is not equal to Chrome and my feeling is that it will
never be. Of course from a distribution perspective, we are trying to create
add-ons and some small patches to make the two come closer. E.g. since recently
we have the widevine capability due to a small patch and an add-on package from
Packman OBS. 

> In Google Chrome Help -> About I read:
> 
> Version 48.0.2564.103 (64-bit)
> 
> In Chromium it is:
> 
> Version 48.0.2564.82 (64-bit)

And this is what I suspected already. Your Chrome version is one stable build
ahead of the Chromium package. Due to a delay in delivering the tarballs, I
only was able to build the 103 build yesterday and will submit it today to
Leap. Hopefully you would get it towards the end of the week. 

You could test however the new build by getting it from the network:chromium
repository, otherwise you have to wait for the update.