You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using uBlock0 0.9.9.2 on SeaMonkey 2.33.1 on Windows XP, I'm seeing an issue where the contents of the 3rd-party filters tab is as expected on initial install, but is blank after the browser is restarted. Toggling the "auto-update filter lists" and "parse and enforce cosmetic filters" checkboxes on and off eventually allows the "Apply changes" button to show up, but clicking "Apply changes" doesn't seem to do anything and the cursor just shows the hourglass icon. The only way to fix this appears to be resetting uBlock0 to the default settings every time.
Steps to reproduce (from a fresh SeaMonkey install):
Launch SeaMonkey
Install uBlock0
Go to uBlock0 Dashboard -> 3rd-party filters
Verify filters are as expected
Restart SeaMonkey
Go to uBlock0 Dashboard -> 3rd-party filters
Filters are no longer listed
For what it's worth, uBlock 0.9.5 doesn't seem to have this problem. From the comments, it would appear that commit uBlock-LLC/uBlock@d9b23d4 had something to do with it.
The text was updated successfully, but these errors were encountered:
Using uBlock0 0.9.9.2 on SeaMonkey 2.33.1 on Windows XP, I'm seeing an issue where the contents of the 3rd-party filters tab is as expected on initial install, but is blank after the browser is restarted. Toggling the "auto-update filter lists" and "parse and enforce cosmetic filters" checkboxes on and off eventually allows the "Apply changes" button to show up, but clicking "Apply changes" doesn't seem to do anything and the cursor just shows the hourglass icon. The only way to fix this appears to be resetting uBlock0 to the default settings every time.
Steps to reproduce (from a fresh SeaMonkey install):
For what it's worth, uBlock 0.9.5 doesn't seem to have this problem. From the comments, it would appear that commit uBlock-LLC/uBlock@d9b23d4 had something to do with it.
The text was updated successfully, but these errors were encountered: