Two Bugs related to clicking NoScript icon before page loads
Posted: Mon Dec 18, 2017 1:04 am
BUGs in Noscript.
NoScript v10.1.5.9 (these bugs have also appeared in earlier versions)
Firefox v 57.0.2
Windows 7
The bugs show themselves in two ways, but I think both ways
are timing related.
The FIRST way the bug shows itself is when I navigate to a site
that only has a few scripts (such as hackademix.net).
Before the site is completely loaded,
if I quickly single click the NoScript icon in the Firefox bookmarks bar,
instead of the expected dropdown appearing with permissions for various URLs,
I get a dropdown with the message "In order to operate on this tab,
NoScript needs to reload it. Proceed?" There are OK and Cancel buttons.
The bug does not occur every time, but I can usually make it happen
once out of 10 tries. Navigate to page, click Firefox reload icon, then
quickly single click the NoScript icon (before the page loads and dropdown appears).
The SECOND way the bug shows itself is when I navigate to a site
that has many scripts and takes many seconds to load.
While the site is loading, if I quickly click
the NoScript icon in the Firefox bookmarks bar MULTIPLE TIMES,
then instead of getting a dropdown (showing URLs),
I will get the contents of the dropdown in a separate window
(with re-sizable frame, title bar, and min/max/close icons
on the right side of the title bar).
This window is independent of the Firefox window,
and it can be moved, re-sized, covered by other windows,
shows up in the Windows taskbar, and will remain open when
the Firefox window is closed). The title bar says:
mox-extension://d05b5c18-27f3 ... ef30 - NoScript Settings - Mozilla Firefox
Sometimes client part of this window shows the list of permissions (URLs), and sometimes
that part is blank. The client portion of the window has the usual
NoScript close, reload, and options icons in the upper left,
and the Revoke Temporary and Temporarily Allow icons
in the upper right.
The bug does not occur every time, but I can usually make it happen once
out of 10 tries. While navigated to a desired page (with many scripts that takes
several seconds to load) ... first click the Firefox reload icon, then click
the NoScript icon multiple times while Firefox shows that the page is
being loaded (reload icon has changed to X). Note that sometimes the separate
window will appear "on top" and be quickly visible, and sometimes the separate window
is "under" the Firefox window. You may have to check the Windows taskbar,
or minimize Firefox, to see if the separate window exists.
Again, my guess is that these two bugs are caused by a timing issue that occurs when
the user clicks the NoScript icon before the page is fully loaded.
Suggested solution: disable (grey out) the NoScript icon while
the page is being loaded, and re-enable the icon once the page
has been fully loaded. In that way, if a user mistakenly clicks the
NoScript icon while the page is being loaded, it will have no effect.
If it is not possible to disable the NoScript icon while page is being loaded,
then perhaps you can disable mouse/keyboard input while page is being loaded?
Can anyone else reproduce these bugs?
NoScript v10.1.5.9 (these bugs have also appeared in earlier versions)
Firefox v 57.0.2
Windows 7
The bugs show themselves in two ways, but I think both ways
are timing related.
The FIRST way the bug shows itself is when I navigate to a site
that only has a few scripts (such as hackademix.net).
Before the site is completely loaded,
if I quickly single click the NoScript icon in the Firefox bookmarks bar,
instead of the expected dropdown appearing with permissions for various URLs,
I get a dropdown with the message "In order to operate on this tab,
NoScript needs to reload it. Proceed?" There are OK and Cancel buttons.
The bug does not occur every time, but I can usually make it happen
once out of 10 tries. Navigate to page, click Firefox reload icon, then
quickly single click the NoScript icon (before the page loads and dropdown appears).
The SECOND way the bug shows itself is when I navigate to a site
that has many scripts and takes many seconds to load.
While the site is loading, if I quickly click
the NoScript icon in the Firefox bookmarks bar MULTIPLE TIMES,
then instead of getting a dropdown (showing URLs),
I will get the contents of the dropdown in a separate window
(with re-sizable frame, title bar, and min/max/close icons
on the right side of the title bar).
This window is independent of the Firefox window,
and it can be moved, re-sized, covered by other windows,
shows up in the Windows taskbar, and will remain open when
the Firefox window is closed). The title bar says:
mox-extension://d05b5c18-27f3 ... ef30 - NoScript Settings - Mozilla Firefox
Sometimes client part of this window shows the list of permissions (URLs), and sometimes
that part is blank. The client portion of the window has the usual
NoScript close, reload, and options icons in the upper left,
and the Revoke Temporary and Temporarily Allow icons
in the upper right.
The bug does not occur every time, but I can usually make it happen once
out of 10 tries. While navigated to a desired page (with many scripts that takes
several seconds to load) ... first click the Firefox reload icon, then click
the NoScript icon multiple times while Firefox shows that the page is
being loaded (reload icon has changed to X). Note that sometimes the separate
window will appear "on top" and be quickly visible, and sometimes the separate window
is "under" the Firefox window. You may have to check the Windows taskbar,
or minimize Firefox, to see if the separate window exists.
Again, my guess is that these two bugs are caused by a timing issue that occurs when
the user clicks the NoScript icon before the page is fully loaded.
Suggested solution: disable (grey out) the NoScript icon while
the page is being loaded, and re-enable the icon once the page
has been fully loaded. In that way, if a user mistakenly clicks the
NoScript icon while the page is being loaded, it will have no effect.
If it is not possible to disable the NoScript icon while page is being loaded,
then perhaps you can disable mouse/keyboard input while page is being loaded?
Can anyone else reproduce these bugs?