Closed Bug 1118459 Opened 10 years ago Closed 9 years ago

[e10s] ABP contentPolicy.js line 625 throw an exception.

Categories

(Firefox :: Extension Compatibility, defect)

Product:
Firefox
Component:
Extension Compatibility
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: ally, Unassigned)

References

Details

also throws on line 404 (bug 1118457)
OS: Windows 8 → All
Hardware: x86_64 → All
Summary: [e10s] ADP contentPolicy.js line 625 throw an exception. → [e10s] ABP contentPolicy.js line 625 throw an exception.
tracking-e10s: --- → +
For reference, line 625 is:

>  for (let node of nodes)

Here nodes is an array of content DOM elements. Elements are being added to this array from the nsIContentPolicy.shouldLoad() implementation, the code here runs asynchronously via Services.tm.currentThread.dispatch() however - that's the first line accessing a content element. I'm pretty sure that this is a duplicate of bug 1118457 so please keep the general discussion there.
This particular contentPolicy.js functionality no longer relies on CPOWs as of Adblock Plus 2.7, is this issue still present?
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.