-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore/Reset settings do not work on Yandex for Android #1009
Comments
Translated: |
Yandex browser issue? Works fine in Fennec. |
I cannot save in Fenix (no effect after clicking on button), can someone confirm this? Restoring and resetting seems to work. |
It's a known issue in Fenix: https://bugzilla.mozilla.org/show_bug.cgi?id=1626349.
Did this ever work? If so, in which earliest version did it stop working? Somebody will have to investigate and find the cause of this. The restore and reset features share similarities, they both delete all storages and restart the extension, so it should be assumed that whatever break restore is also what break reset. Reset is quite simple, so somebody needs to narrow down which of those calls fails and what would be the fix. |
This comment has been minimized.
This comment has been minimized.
From Google store uBlock Origin development build v1.26.3b16 |
There's a problem with yandex and kiwi |
So if I get this correctly, the restore/reset features work fine with uBO 1.26.3b16, installed from the Google Chrome store. However the Google Chrome store currently serves uBO 1.26.3b18. You report that It does not work correctly with uBO 1.26.3b19. You installed uBO 1.26.3b19 from where? How did you install this version? |
|
|
1.26.3b20 is now available in the Chrome Web Store. If you install it from there, do you still suffer the same issues? |
Sorry, it's a browser problem. The new version of yandex browser 81.0.4044.219 beta has this problem. It's normal to install yandex browser 80.0.3987.90 |
yandex手机版本uBlock Origin development build v1.26.3b19可以备份设置,但是无法从从备份还原,重置为默认设置也无法使用
The text was updated successfully, but these errors were encountered: