For this reason I'll limit the MBG profile to Malwarebytes Browser Guard alone, no other extension. Whilst there's no identifiable conflict with the off/on method, I don't rule out the possibility of something more subtle causing the misbehaviour – this is (generally) as true for a supposedly pure WebExtensions APIs environment as it is for environments where legacy extensions are in the mix. After a while, symptoms reappeared it's this profile in the screen recording above.īoth the test profile, and my default profile, have been through automated Extension Conflict Troubleshooter routines – methodically disabling and re-enabling subsets of extensions. Neither did it occur following a refresh of a previously affected 'test' profile. The double-blocking does not occur when extension version 2.1.3 is added to a new 'MBG' profile. Waterfox Classic falls just below this line, but does include most of what was associated with Firefox 57.0 (through its 56.0.2 origin, plus some backporting). – there's the strict_min_version of 57.0 (i.e.
0 kommentar(er)
