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
The corresponding PR has to be created in the controller repo.
Since the chrome alarms have to be used only for the extension, we would have to configure them at the API level to differentiate extension using mv3 from mobile and extension using mv2.
Can we introduce a new optional state variable with true value to identify extension with mv3 and use chrome alarms in that case?
Closing this PR as the PhishingController does not require polling anymore.
Quoting Mark's comment on the same from the channel
Mark Stacey
In some of these cases we can remove the polling altogether. We just did that for the phishing controller, for example. That can be removed from the list, as now it lazily fetches the config when it detects that it has been too long since it last checked.
Replace setTimeout for polling in updatePhishingLists() in PhishingController in a time window of 60 minutes.
The text was updated successfully, but these errors were encountered: