Opened on 10/29/2018 at 03:12:55 PM
Closed on 08/29/2019 at 05:43:18 PM
#7078 closed defect (rejected)
Block element sometimes causes console errors
Reported by: | Ross | Assignee: | |
---|---|---|---|
Priority: | P3 | Milestone: | |
Module: | Platform | Keywords: | closed-in-favor-of-gitlab |
Cc: | sebastian, kzar | Blocked By: | |
Blocking: | Platform: | Unknown / Cross platform | |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description
Environment
ABP 3.3.2.2176
Chrome 70 / Windows 10
Firefox 63 / Windows 10
How to reproduce
- Open a site like reddit, enter block element mode.
- Switch around other browser tabs, open new ones, close some.
- Go back to the block element tab and block an element/accept the filter.
Observed behaviour
Sometimes, but not always, the following errors appear in the browser consoles:
In Chrome 70 (background console):
Unchecked runtime.lastError while running browserAction.setIcon: No tab with id: 329263172.
In Firefox 63 (browser console):
NS_ERROR_NOT_INITIALIZED: ext-windows.js:16
TypeError: Argument 1 of PrecompiledScript.executeInGlobal is not an object. ExtensionContent.jsm:501:18
Error: port.onDisconnect.hasListeners is not a function content.js
-- or --
Promise resolved after context unloaded include.preload.js:864
Promise resolved after context unloaded apply.js:63
TypeError: Argument 1 of PrecompiledScript.executeInGlobal is not an object. ExtensionContent.jsm:501:18
Error: port.onDisconnect.hasListeners is not a function
Expected behaviour
Errors to not occur / be handled (if possible).
Attachments (0)
Change History (4)
comment:1 Changed on 10/29/2018 at 03:14:23 PM by Ross
comment:2 Changed on 10/29/2018 at 04:47:48 PM by kzar
- Component changed from Unknown to Platform
- Priority changed from Unknown to P3
- Ready set
comment:4 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.
Block element still seems to be working fine, just the errors occur. I'm having difficulty reproducing them (more so on Chrome) so thought I would report the ones I had. I'm not sure exactly which errors are relevant.