Hi Randy,
Thanks for the feedback. Believe me that I am not happy with Chrome updates either, but I cannot control Chrome releases or changes. You can still use an older chrome build, but not sure if they are available for download or not.
FOP2 is using state of the art technology. That is the price to pay if you use state of the art tech, Anyways, I could add a configuration switch to force the use of adobe flash, perhaps I will add that on the next release. That will permit you to use chrome but not taking advantage of the much faster html5 websockets implementation.
If a browser adds ore removes or changes support for some feature it is not my responsibility. If a user updates a browser, it is not my responsibility, If the browser updates itself, it is still not my responsibility. You have choices, you can still use other browsers.
What I will have to do is to streamline the work with Elastix so I can push new rpms at the same time I release new versions. That involves also a lot of additional work, packaging software is not something easy and it is very time consuming. I will try to do that in the next week, before Elastixworld.
Best regards,
