On Sun, Aug 7, 2016 at 5:35 AM, Rex Dieter <rdieter@math.unl.edu> wrote:
In my prior post, I included chromium in the list of browser candidates.  If
you're not familiar with it, it is essentially a free version of google
chrome that recently made it's way into fedora package repositories.

Disclosure:  I'm a extensive user of Chrome and very much tied into the Google ecosystem.

I believe first that someone needs to clarify a bit on what we're trying to do here.  What is the
criteria for the Fedora default browser.  At a very high simplistic level, if we're wanting something
Qt'ish then the answer is qupzilla... if we're looking for something that would attract more Chrome
users - then it would be Chromium.

Whichever it is, we need to make sure that it is kept current.  I don't want to be stuck at Chromium
52 when Chrome 53 has been released.  

Another thing to keep in mind is compatibility.  Check out the bug I created here:

It's related to the use of Google Music.  Yes, I know that everyone might not use it, but
it shows the quirkiness of the current version of Chromium in Fedora.  To be fair, I did find the
same issue in the current stable version of Vivaldi - but, it has since been fixed in the beta versions.
As I noted in the bug report... it works perfectly fine in current version of qupzilla and the Chromium
version in the russian fedora repo.  This is not a slam, but the inability to identify and resolve an issue
with Google Music in Chromium of all things, especially when it is working in qupzilla is a bit concerning.

As much as I'm a cheerleader for all things chrome, I wouldn't choose it to be a default
without these things resolved - and saying that "Chromium is complicated" doesn't give it a pass.