forum/viewtopic.php?p=88091#p88091
by Noggie » Thu Dec 05, 2013 3:47 am
I'm still voting adblock to implement an import/export function and start backing up the most important settings on a different storage option, such as the old one adblock used before switching over to this new buggy storage api.
Important settings: everything except custom white list domains and custom rules because those will not fit if they get over 2-4KB, which they can get.
chrome: import / export for ABP settings
adblock save feature
Thank you.
Although a bit of nitpicking. I mentioned two feature requests.
1. import/export settings feature
2. adblock backups its settings to other storage api's. If the settings disappear adblock can check and read the settings from the other storage api's
Chrome do not allow full filesystem access so loading custom filters and whitelised domains from a file will not work.
But it do allow sandboxed access through chrome.fileSystem http://developer.chrome.com/apps/fileSystem.html
Adblock could backup the custom filters and whitelisted domains to that. I do not know if chrome.fileSystem is also buggy though.
Although a bit of nitpicking. I mentioned two feature requests.
1. import/export settings feature
2. adblock backups its settings to other storage api's. If the settings disappear adblock can check and read the settings from the other storage api's
Chrome do not allow full filesystem access so loading custom filters and whitelised domains from a file will not work.
But it do allow sandboxed access through chrome.fileSystem http://developer.chrome.com/apps/fileSystem.html
Adblock could backup the custom filters and whitelisted domains to that. I do not know if chrome.fileSystem is also buggy though.