3 ms·

Is it really Chrome or is it the new "pepper" plugin API driving this? ie. if other browsers decide to support the new plugin API, will Adobe also support them

by zmmmmm 15y ago

Is it really Chrome or is it the new "pepper" plugin API driving this? ie. if other browsers decide to support the new plugin API, will Adobe also support them too?

tyleregeto 15y ago
The API was developed jointly by Adobe and Chrome, so its not Chrome or the API causing it, it's both parties wanting a better solution. It makes it cheaper for Adobe to support more platforms with less development hours. Adobe has stated (not in any press releases, but from the mouth of employees) that they will work with any other browser wanting to implement the same API.