You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On src/utils.js the util function waitForElement observes a given target node in order to catch a certain element once it's being added to the target node.
However, when it actually looks for the existence of said element it uses document.querySelector rather than target.querySelector. This occurs twice - on the precheck before observing and in the observer callback.
This may lead to a bug when an element which isn't a child of the target node would be incorrectly returned.
The text was updated successfully, but these errors were encountered:
On src/utils.js the util function
waitForElement
observes a given target node in order to catch a certain element once it's being added to the target node.However, when it actually looks for the existence of said element it uses
document.querySelector
rather thantarget.querySelector
. This occurs twice - on the precheck before observing and in the observer callback.This may lead to a bug when an element which isn't a child of the target node would be incorrectly returned.
The text was updated successfully, but these errors were encountered: