During the following years I witnessed with a lot of sadness a couple of websites that would work out-of-the-box just fine with Chrome and not on Firefox. No worries, as it was not too hard to make them work in Firefox too, also HTML5 was becoming a thing so I hoped that somewhere down the line every audio and video format alongside their secure streaming service would become open.įor years I patiently waited until 2015 when it finally happened: I could only watch Netflix on Google Chrome and not on Firefox.
Then came streaming services became popular and the first difference became apparent: Google's browser offered support for privative sound codecs and then video too. About that time I first came across Google Chrome, but it was not anything shiny or better from what Firefox already had to offer on Linux.
It only works when the Web client is installed through the Web browser page.By the end 2008 I went full-Linux user (and I still am) with no dual-boot. Note: The Firefox plug-in update feature does not work if you install the native Windows Client. Users who install the plug-in with Mozilla Firefox can update the plug-in through Firefox’s Add-on manager. If the user does not have sufficient rights to install browser add-ons (the user is running Internet Explorer and is not an administrator or power user), the client should be installed using the FH Web Edition Client Setup Program. If users have power-user rights, are running the ActiveX Control, and connect to a FH Web Edition server with an updated client, the ActiveX control updates automatically. The Web pages install and update the Web clients as long as the user has sufficient rights to install browser add-ons. If FH Web Edition was deployed through a Web browser’s Add-on manager, users should launch a Web browser to access a FH Web Edition Web server. You are here: Updating the ActiveX control and the plug-in
0 kommentar(er)
