Closed Ascrod closed 6 years ago
Still looking at this issue. It has to do with how page load events are listened to here:
The events mentioned above fire correctly, but the code for handling them (as well as the MozAfterPaint
event) is faulty. The issue lies in the use of gBrowser
and content
with the assumption that the tab firing the events is the currently selected tab.
I think most of this can be resolved by using gBrowser.getBrowserForDocument
with the target document passed in with the event.
Resolved with 0667ae43454fc2cf8a5c0703661c414b925f1af1.
See also: https://forum.palemoon.org/viewtopic.php?p=129429#p129429