I'd like to explain why supporting Chromium is literally same thing as supporting Chrome.

To explain this, I'd like to give you some simplified explanation on how Chrome and Chromium projects are related to each other. All of you most probably know what Google Chrome browser is. But did you know how it gets developed? If you open up Google Chrome about page (chrome://settings/help), you will see statement like this "Google Chrome is made possible by the Chromium open source project and other open source software.". See this reference to Chromium here? That's it.

So in general Chromium is parent project to Chrome. That is where the browser gets developed. Chrome utilizes this codebase (without altering core features), adds several things on top of it (some proprietary codecs, flash support and so on) and is then distributed by Google to all the platforms. You can see more details here: The Difference between Google Chrome and Chromium on Linux or in Wikipedia.

So unless your product depends on those proprietary pieces that are distributed with Google Chrome (and Lifesize does not, as far as I can say), there is no reason to ban Chromium. Chrome is otherwise fully compatible with Chromium and vise versa.

Fellow developers, please consider allowing the community to use open-source parent of Google Chrome to access Lifesize webapp.

You should be able to use our WebApp with any newer version of Chrome or Chromium on most desktops, including Linux. In fact, we use Chromium as the core of our downloadable applications.

We don't presently officially support our WebApp on Linux, but we know of many people that successfully use it in those environments. Our advice is to give it a try and see if it works for you. If you run into Linux specific issues, feel free to post on community and we'll see what we can do to get you going on the WebApp.

Hi Daniel, I noticed that 2 different builds are available here: Download latest stable Chromium binaries (64-bit and 32-bit) . One which includes WebRTC and one which does not. Though, it also looks like the version numbers are identical. Is there any chance you installed a build of Chromium which does not include WebRTC?

I didn't receive the attachment. If you tried to attach it within an email response to the idea, I'm not sure that works. I'm not seeing an easy way to attach a file to this idea here in community. You can attach to discussions and documents, but doesn't look like we can attach a file to an idea. Looks like that ability is limited. You can send it to me directly at mtorok@lifesize.com, or you could also take a screen capture and attach that as a picture, too.

I've reached out internally to try to find you a solution. I'm guessing it might have to do with WebRTC 1.1 having ORTC support, but that is a complete guess. I also noticed that you are running without a recognized web cam. Would you mind attaching one and seeing if that resolves the issue. I'm waiting on answers from my side, but these 2 things stood out in your report.

**Update** I don't think ORTC is the issue as my version of Chrome doesn't support it.