Opened on 08/24/2017 at 11:33:57 AM
Closed on 08/24/2017 at 07:31:33 PM
Last modified on 08/29/2017 at 12:40:53 PM
#5562 closed change (fixed)
Move Edge storage to IndexedDB
| Reported by: | oleksandr | Assignee: | oleksandr |
|---|---|---|---|
| Priority: | Unknown | Milestone: | |
| Module: | Platform | Keywords: | |
| Cc: | sebastian, kzar | Blocked By: | |
| Blocking: | Platform: | Edge | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by kzar)
Background
With #5315 we have added support for Microsoft Edge to the adblockpluschrome master bookmark. However builds from that code result in a very sub-optimal extension because using storage.local for storing filter lists is very slow in Edge. Even the latest Windows Insider builds (16273, August 23rd 2017) have this issue, so it is unlikely to get fixed in the Fall Update.
In #4721 we have already implemented the code to use IndexedDB for storage of filters in Microsoft Edge. It is working much faster, so we should move to that.
What to change
Change filter list storage mechanism for edge bookmark to IndexedDB.
Hint for testers
We want to make sure that we don't lose user's settings when updating from previous versions of ABP for Edge. So making sure the custom filters, whitelisted domains and selected filter list is a good idea. Also just generally making sure the storage works as expected would be appreciated.
A commit referencing this issue has landed:
Issue 5562 - Use IndexedDB for storage in Edge bookmark