I'm not sure if you can roll back the change from toolbar to button/menu simply by switching to Firefox 52 ESR. The Extended Support Release of Firefox 52 will continue to run old-style extensions and get security updates through next June. The last regular release of Firefox that will support old-style extensions is Firefox 56, so that doesn't take you very far. But is the drop-menu less complete than the old horizontal toolbar? Obviously it's an extra step to access a drop-down menu than to click a displayed button on a bar. IMO, Mozilla is looking for parity with Google Chrome, ''(no longer a trail browser with Firefox as it once was, now a copy cat or mimic of what more popular have done - meeting the lower standards of what users want or expect)'' to make it easier for developers to create one extension for most all browsers, with little additional work to adapt it to each specific browser brand So we will need to get used to Firefox not being as extensible as it has been. WebExtensions just aren't as powerful as the traditional Firefox extensions have been. Smacks of the New Coke debacle back in April 1985, which was discontinued in 1992. I plan on waiting until after Firefox 60 comes out before I waste much time trying to config the "new" Firefox to my liking. So I am still using an old ESR 38 version for my "heavy lifting" from before the "signing" thing started my extensions dropping like flies. Overall, as a 15 year user from the days of Phoenix 0.3, I am not happy with what I see and have been seeing for quite awhile now. It's possible that the new API's may not be complete yet and more features may be added down the road and user requests made in the proper place, with the attitude, might restore some what might be lost or add new stuff later on. IMO, Mozilla is looking for parity with Google Chrome, (no longer a trail browser with Firefox as it once was, now a copy cat or mimic of what more popular have done - meeting the lower standards of what users want or expect) to make it easier for developers to create one extension for most all browsers, with little additional work to adapt it to each specific browser brand Their scheme with the "lifetime" being for a limited time pissed me off - so I stopped using it. You won't be missing out on much protection frankly just because of the way this module works.I can't comment specifically about Roboform, haven't used it for many years now. I would advise anyone having the issues described in this thread to do the same until this issue is resolved. Ransomware Protection tends to cause the most conflicts and drags down system performance more than any other component or module in Malwarebytes and is simultaneously the least proactive in actually preventing infection so I keep it disabled at all times. It is a secondary layer of defense that functions as a last resort should the system become infected with ransomware, however most ransomware uses methods of infection that are well covered by the other components in Malwarebytes such as exploits which are very well covered by Exploit Protection. This means that if the other components of protection are doing their jobs of actually preventing infections from ever installing/becoming active on the system you will never see a detection from the Ransomware Protection component. It is by far the least proactive/protective component in Malwarebytes because all it does is monitor memory/active processes and threads for ransomware behavior to catch ransomware in the act. You can keep Ransomware Protection disabled. I never had this problem with MB 1.0.770. I use Roboform many times during the day. After correcting the problem I get the real full functioning interface.įor me this is a show stopper. Interestingly, the same problem does not occur with the Roboform extension for Firefox.Īccording to Roboform support, the interface I get when the problem happens is a limited interface with only partial functionality. This problem of course also happens anytime I reboot the system and Chrome starts up. At his point I could turn Ransomware protection back on and all worked fine until the next time Google Chrome was closed and re-opened. To correct the problem I had to turn off Ransomware protection, disable the Roboform extension, re-enable the Roboform extension and then it loaded successfully. When closing and re-opening Chrome, the Roboform extension fails to load successfully which results in getting the wrong interface. So it is not just on the install of the Roboform extension so I wonder if the title of this thread should be changed to something like "Ransomware protection interferes with loading of Roboform extension". I closed Google Chrome and re-opened it and had the same problem. The problem is more widespread than I thought.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |