Open vitonsky opened 3 years ago
Hack to make available Linguist for Tor Browser 11.0.6 and newer
about:config
dom.indexedDB.privateBrowsing.enabled
dom.storage.enabled
uBlock Origin are works fine in Tor Browser. We should research how it keep rules in persistent storage, maybe it possible to use this way for our storage
We may just disable features which is require a indexDB. We may test indexDB support while first start and if it's not support, disable these
Using Mullvad Browser (based on Tor Browser but without the tor protocol) and both options are by default enabled. However, the extension overlay fails and so does the options page. Any idea on how to make it work?
@sanjayen please give more info about your case
about:debugging#/runtime/this-firefox
and click inspect
on Linguist, then open tab Console
)@vitonsky apologies, should have shared earlier. Here it is;
browser name and version: Mullvad Browser 13.0a3 - https://github.com/mullvad/mullvad-browser/releases/tag/13.0a3 operating system info: Windows 11 Pro 22H2 OS Build - 22621.2215
Both configs - dom.indexedDB.privateBrowsing.enabled and dom.storage.enabled have already been enabled, by default, in Mullvad.
@sanjayen thank you for info, i will investigate and come back
Can't open popup for translate page, can't open dictionary
Inspector log: "A mutation operation was attempted on a database that did not allow mutations"
Solution: use
browser.storage.local
instead indexDB everywhere when it possible, we must use indexDB only for optional cache and other improvementsThe real problem
This components are use indexDB
To fix this problem its all should stop use indexDB. It is not possible because indexDB is most efficient method of store data.
Consequent, this problem will not fix if we can't disable only dictionary, translators cache and site preferences.
Task
We must research whats features we should disable to make it work.
If you want make it work in tor, you can research it and write in comments about results