Chrome encourages users to use Google products, and create a Google account to be tracked by. Google wants to control the browser market so they can push the technologies important to them, and also push Google services and data collection. If I had to guess what their real motivation is, it's probably to force the last 7%-9% of people using Internet Explorer to Chrome and motivate new pc/chromebook sales. The cost of keeping obsoleted layouts available is minimal. all allow their users to opt out of their redesigns and switch back. It's just a shame because Twitter, Reddit, Deviantart etc. It will just be slower/more power consuming (especially on older hardware with weaker graphics chips) and harder to use (especially on not-widescreens thanks to the inflated padding). I did not try that option since I had already installed pale moon.Chrome49 should handle polymer just fine. By adding a symbolic link in /usr/lib/mozilla pointing to the location of the vlc plugin I am able to successfully view my cameras, as long as pale moon does not make the npapi obsolete.Īlso of note is suggestion by hmjgriffon to use chrome with NACL plugin. I found that file in "/usr/lib64/browser-plugins". The pale moon FAQ indicated the location searched for plugin's. Since my camera's are not routed outside of my firewall, I can use this browser for the sole purpose of occasionally viewing their output with vlc without modifying FF. That worked in FF but since I use FF all the time I'd prefer it as the developers intended.Īs suggested by user 'tangent', I installed the 64bit linux version of pale moon. Was able to use suggestion in thread psa-firefox-and-hikvision-web-component.17618/#post-166896 to add boolean string to about:config. Using linux 64 bit FF v52 no longer works due to Mozilla deprecation of npapi. I was thinking that perhaps a path of /usr/lib/mozilla referred to 32 bit instead of 64 bit.
0 kommentar(er)
