4 ms·

The problem is that Chrome remove features without providing any viable replacement. For example Flash: currently the Chrome audio APIs do not cover all of the

The problem is that Chrome remove features without providing any viable replacement. For example Flash: currently the Chrome audio APIs do not cover all of the functionality provided by Flash. You cannot, for example, pause the recording of audio. If you have a product which requires that functionality then you're stuck. You can't upgrade. In the recent past I was in just that position: we had no choice but to block Chrome upgrades, at least until such a time as we could implement the functionality ourselves. It would be much better if Chrome would just leave the functionality in there; or maybe provide a special "Enterprise" build which includes all of the features behind feature flags. All they need to do is make that configurable by Group Policies and you've made Enterprises happy (and we can keep upgrading the core browser).

nothrabannosir 10y ago
> You cannot, for example, pause the recording of audio. You can use the Web Audio API (getusermedia) and set an audio pipeline filter that stops sending data while a boolean flag is set. I don't know if you mean a different API entirely, and I don't mean to disagree---just FYI :)
- radicalbyte 10y ago
  Thanks, that is indeed so. I must say that the Chrome team have been really fantastic about it (they reached out to me after asking on twitter). It's just the age old resources problem: not only do you have to change the frontend, you also need to make changes on the server. That more than doubles the work (quadruples in our case because the server requires far more QA effort). That comes at the cost of other features, features which are more valuable.
johnward 10y ago
I've had discussions internally and the it staff basically said they will not considered actual support for Chrome. However they let us install any browser and support reps just instruct people to use certain browsers for antiquated software.
coredog64 10y ago
Chrome can't kill Flash fast enough. I'm stuck with AppD, and the sooner that Chrome highlights what a festering pile of garbage their web portal is, the better.

nothrabannosir 10y ago

> You cannot, for example, pause the recording of audio. You can use the Web Audio API (getusermedia) and set an audio pipeline filter that stops sending data while a boolean flag is set. I don't know if you mean a different API entirely, and I don't mean to disagree---just FYI :)

radicalbyte 10y ago
Thanks, that is indeed so. I must say that the Chrome team have been really fantastic about it (they reached out to me after asking on twitter). It's just the age old resources problem: not only do you have to change the frontend, you also need to make changes on the server. That more than doubles the work (quadruples in our case because the server requires far more QA effort). That comes at the cost of other features, features which are more valuable.

johnward 10y ago

I've had discussions internally and the it staff basically said they will not considered actual support for Chrome. However they let us install any browser and support reps just instruct people to use certain browsers for antiquated software.

coredog64 10y ago

Chrome can't kill Flash fast enough. I'm stuck with AppD, and the sooner that Chrome highlights what a festering pile of garbage their web portal is, the better.