chromium has patches but they refuse to implement them for some weird reasons, you can happy implement them and add a flag and keep that flag on disable, but when you don't want to do it. To be honest this might be the last drop for me regarding Firefox:ġ) they are unable or refuse to make their browser render properly some sites (got tired to report to Firefox the sites and see how they totaly ignore the problem, yes I reported 2 times/year in the last 6 years the same sites over and over just to see how they happy ignored the reports) while Chrome (or other Chromium based browser) and IE display them correctly (I gave up this year to report them, I'm 100% sure that after 10 reports for each of the sites with no fix in the last 6 years it just won't happen)Ģ) they can't even check their certificate expiration dateģ) bookmarks that go by default to "other bookmarks" folder (need to use an add-on to change this abnormal default behaviour and surprise surprise that add-on is not working by default atm)Ĥ) weird performace issues regarding HTML5 and GCN gpu + some drivers (basicaly with some drivers it refuses to use gpu hardware acceleration despite the fact that those drivers are not in the excluded list.), something that doesn't happen with Chrome (or other Chromium based browser) or IE (this is Windows case, I don't talk about Linux where nobody trully bothered to implement gpu hardware acceleration, it can be done but apparently all browser engines refuse to do it. Once at the setting, you should toggle the setting to false by double-clicking on it. To do this from the Developer or Nightly builds, you can go to about:config and search for. Method 2: Install Firefox Nightly or Developer buildsĪnother option is to install the Developer or Nightly version of Firefox as these versions have the ability to disable the signature requirement for extensions. While this will work, it will also mean any site you go to with a certificate that expired today would work as well, your emails from a local mail client will have the wrong date, and some sites may show the wrong date. The easiest method is to just turn your clock back a few days so that the certificate is not expired.
If addons are not that important to you, you can just wait for Mozilla to resolve the issue and your addons will start working again.įor those who do not want to wait and want to enable their installed extensions immediately, you have a few options: Method 1: Turn your clock back a few days Mozilla looking into issue Getting your addons working again
0 kommentar(er)
