Closed Bug 1118465 Opened 9 years ago Closed 8 years ago

{[e10s] ABP's objectTabs.js also throws an exception on line 364.

Categories

(Firefox :: Extension Compatibility, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
e10s + ---

People

(Reporter: ally, Unassigned)

References

Details

Also note that object tabs regularly on line 302 (bug 1118462)
OS: Windows 8 → All
Hardware: x86_64 → All
Summary: {[e10s] ADP's objectTabs.js also throws an exception on line 364. → {[e10s] ABP's objectTabs.js also throws an exception on line 364.
tracking-e10s: --- → +
For reference, line 364 is:

>      let wndWidth = doc.documentElement.clientWidth;

doc is a content document here, and judging from the similar bugs the exception is triggered by accessing doc.documentElement. Interestingly, before getting here Adblock Plus will necessarily access other elements (calling getBoundClientRect() on them and accessing element.ownerDocument), and that access apparently doesn't trigger an exception. However, the code walks the frame hierarchy so maybe the issue affects only elements of a particular frame. I'm pretty sure that this is a duplicate of bug 1118457 so please keep the general discussion there.
objectTabs.js no longer relies on CPOWs as of Adblock Plus 2.7, is this issue still present?
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.