Opened 3 years ago

Closed 3 years ago

#5098 closed change (fixed)

Expose FilterStorage initialization state

Reported by: trev Assignee: trev
Priority: P1 Milestone:
Module: Core Keywords:
Cc: Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):



Adblock Plus for Firefox was previously relying on FilterStorage._loading to recognize an uninitialized filter storage. Now that this flag is gone it will occasionally start first-run actions too early.

What to change

Expose FilterStorage.initialized that is set after the first FilterStorage.loadFromDisk() call completes.

Change History (3)

comment:1 Changed 3 years ago by trev

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:2 Changed 3 years ago by abpbot

A commit referencing this issue has landed:
Issue 5098 - Expose FilterStorage initialization state

comment:3 Changed 3 years ago by trev

  • Resolution set to fixed
  • Status changed from reviewing to closed
Note: See TracTickets for help on using tickets.