Toggling DOM Inspector on/off adds a filter entry in the logger #1960
-
STR --
Firefox 98 and uBO dev build. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
It's because uBO adds an iframe to the page, to render its own overlay, and on the other side this causes an event that a new frame has been added and this causes an evaluation of generichide within that frame (because of |
Beta Was this translation helpful? Give feedback.
-
I doubt this can be fixed. Since I can also reproduce with element picker, in which the content scripts are not injected, this means there is a small window between the frame being added and the location of the frame being set to the element picker HTML, time window in which the frame is seen as a plain |
Beta Was this translation helpful? Give feedback.
I doubt this can be fixed. Since I can also reproduce with element picker, in which the content scripts are not injected, this means there is a small window between the frame being added and the location of the frame being set to the element picker HTML, time window in which the frame is seen as a plain
about:blank
frame, meaning content scripts will be injected in it (because ofmatch_about_blank
in manifest), and hence reported to the logger. There is no way uBO's content script in anabout:blank
can tell whether the iframe is meant to be a container for the element picker (or DOM inspector overlay). But maybe further investigation can prove otherwise. I consider this a really minor iss…