Open alcayaga opened 6 months ago
I only see one location to a place where we disable the skiplegacy option: https://github.com/kheina-com/Blue-Blocker/blob/8ed9701707c2bda5f37b3026e4aa7af809c48111/src/shared.ts#L567
you may not have an answer to this question, and that's ok, but do you know if you a) have users in the queue and b) have a twitter tab open during the BB version update?
the only situation I can see where this gets accidentally disabled is if the update occurs during a block and that timeout above never gets cancelled as it should
Closing for now, feel free to reopen if it happens again or you find out new information about what caused this.
Closing for now, feel free to reopen if it happens again or you find out new information about what caused this.
...do we know which version in particular was affected?
Sorry for the delay in responding.
Since Firefox updates the extension automatically, I can't be certain if there were users in the queue and a Twitter tab open during the updates. However, it is likely, as I usually have a Twitter tab open.
I will monitor the situation and report back if I encounter this issue with the upcoming release. Thanks for your assistance!
Sorry for the delay in responding.
Since Firefox updates the extension automatically, I can't be certain if there were users in the queue and a Twitter tab open during the updates. However, it is likely, as I usually have a Twitter tab open.
I will monitor the situation and report back if I encounter this issue with the upcoming release. Thanks for your assistance!
thanks! just to chime in here, the skip legacy users option is one of the few that can actually disable itself since it relies on an idb database that runs in the background script. while I didn't foresee any issues with the db lookup since it's very quick, if the addon were to update at the same time as a lookup, that might cause a failure and make the extension turn off the setting
we could probably just remove the disable legacy code and just pop an error instead and it would probably fix this
I received the update and the checkbox disabled by itself again. I can confirm I didn't have any user in the queue
Using Edge 125.0.2535.51 on Windows 10
Maybe it's not the updates that trigger this behavior. I checked the settings on the same computer, and it's unchecked again with the same version of the extension.
Could there be some kind of synchronization of the settings that might trigger this as well?
I don't understand, it's still checked here?
I'm not certain how to offer additional evidence, but I suspect there is a connection between extension updates and the 'Skip legacy verified users unchecks when updating' unchecking itself
This is the second instance where I've noticed this option was unchecked, despite my recollection of having checked it previously and not changing it. Interestingly, other settings appear unaffected.
I am sorry I can't provide more information at this moment. However, if helpful, I am willing to assist in diagnosing this issue further.