Unfortunately there are some features we're using that simply would take far far too long to refactor. For example, CSS grids are a new browser feature we use for the entire layout of the editor. Grids are designed specifically for this usage in mind, and if we wanted to make it an optional feature we'd end up with div soup.
I understand your point entirely, but there was a tradeoff here, supporting organisations/users with older browsers, or reduced development time and easier maintenance. Historically we've always gone for #2.
@Tom, I understand what you are going for, but I am not asking for you to support older versions, but simply let the user decide to try it out.
Give it this scenario:
I am a corp that uses managed versions.
I am 1 week out from my delivery window.
A new version of chrome is updated, C3 "forces" you to run on it.
I miss my deadline.
This is one of the inherent risk of using a browser based IDE, they update and can update often. I use to pitch C2 to some companies, but C3 I simply cannot pitch with the forcing of using the latest Chrome version. Updating your OS to the latest and greatest, versus your browser are two different worlds. Something running in the browser should not be locked down like that.
Maybe my understanding is off, but you have not corrected my question. Whether or not the absolutely latest version is required, or if this is just a beta thing. By your responses, it sounds like to me, that C3 will always require the latest version of chrome.
If that is the case, C3 seems kind of...short-sighted. Let me explain what I mean. You are basically saying, C3 is only for the little guys. You have no intention of targeting big corporations, with lots of money to proper development. It gives C3 a bit of a toy-ish feel, as in it is not meant for any serious project. To ignore the managed version control of Chrome, really surprises me.
That is my 2 cents on it. As mentioned, maybe I am misunderstanding you, but this is how I feel about it and my feedback on it.