Opened on 02/09/2018 at 10:31:50 AM
Closed on 08/29/2019 at 05:43:18 PM
#6374 closed defect (rejected)
[webextension] Adblock Plus devtools panel is blank on some sites in Firefox
Reported by: | Ross | Assignee: | |
---|---|---|---|
Priority: | P3 | Milestone: | |
Module: | Platform | Keywords: | closed-in-favor-of-gitlab |
Cc: | kzar, sebastian | Blocked By: | |
Blocking: | Platform: | Firefox | |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description (last modified by kzar)
Environment
ABP 3.0.2.1969
Firefox 59 / Windows 7
How to reproduce
- Navigate to https://kick.media/
- Open the Adblock Plus devtools panel.
- Refresh page.
- Add the RuAdList+EasyList subscription.
- Refresh the page again.
- Close the devtools panel.
- Reopen the devtools panel and refresh the page.
Observed behaviour
The Adblock Plus devtools panel does not always seem to load correctly. Sometimes at Step 3 or 5, none of the requests are displayed in the panel. Nearly always at Step 7 the devtools panel is completely blank without even the filtering dropdowns displayed (see attached screenshot).
(The page is also blank after Step 5, but not sure if that is just filtering issues from RuAdList - See hub ticket 7906).
Expected behaviour
The Adblock Plus devtools panel to reliably load and display what is occuring with the page.
Attachments (1)
Change History (3)
Changed on 02/09/2018 at 10:32:34 AM by Ross
comment:1 Changed on 02/13/2018 at 01:00:48 PM by kzar
- Component changed from Unknown to Platform
- Description modified (diff)
- Priority changed from Unknown to P3
- Ready set
- Summary changed from Adblock Plus devtools panel is blank on some sites in Firefox to [webextension] Adblock Plus devtools panel is blank on some sites in Firefox
comment:2 Changed on 08/29/2019 at 05:43:18 PM by sebastian
- Keywords closed-in-favor-of-gitlab added
- Resolution set to rejected
- Status changed from new to closed
Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.
I can reproduce this, I suspect it's a bug with Firefox's WebExtension API. If that turns out to be the case we should close this issue and open one at bugzilla.mozilla.org instead.