hackademix
Noscript does not display the names of the items to allow or deny
Like the title says - when invoking Noscript to select allow or deny, teh "buttons" are visible, but no name accompanies it to say what it is you are allowing or denying - for instance for this site I see the struck through S, the time S and the full S but I don't see github as the thing I am trying to allow - I get nothing at all.
This has been like this for over two weeks now.
Firefox version?
Can you see any error message popping up in the browser console (ctrl+shift+J) when if open the popup?
Thanks for the reply. The only thing related to noscript is this:
NoScript: apply title="MSG_Close" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 NoScript: apply title="MSG_Reload" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 NoScript: apply title="MSG_Options" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 NoScript: apply title="MSG_Reveal" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 NoScript: apply title="MSG_TempTrustPage" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 NoScript: apply title="MSG_RevokeTemp" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59
Time stamped log file is as follows: 12:05:04.151 NoScript: apply title="MSG_Close" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 12:05:04.156 NoScript: apply title="MSG_Reload" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 12:05:04.157 NoScript: apply title="MSG_Options" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 12:05:04.157 NoScript: apply title="MSG_Reveal" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 12:05:04.157 NoScript: apply title="MSG_TempTrustPage" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11 @moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:64:59 log.js:41:15 12:05:04.158 NoScript: apply title="MSG_RevokeTemp" updateDOM@moz-extension://bf6c4ad7-6fbf-406a-91a9-b7e275c6bdf9/nscl/common/locale.js:57:11
I can see in the screenshot you're opening NoScript's UI in a window (using the keyboard shortcut or the context menu, I guess) rather than the popup from the toolbar icon.
Could you look also for message in that window's own console (ctrl+shift+K while it is in focus)?
As for the update, you can try 12.1.904 from https://noscript.net/getit/#devel
The reason I had to open it in a window was to capture it for you to see. If I try to do so from the pop-up the pop-up disappears when I active a screen capture, that was the only reason. Strictly a practical solution to getting an image to post. The update seems to have helped, getting the text again, finally. Odd, that. Many thanks again. Noscript is one of the great blessings in the Internet swamp. Always a great fan, and I appreciate the rapid help. You are a super guy.
The reason I had to open it in a window was to capture it for you to see. If I try to do so from the pop-up the pop-up disappears when I active a screen capture, that was the only reason. Strictly a practical solution to getting an image to post.
I've noticed the same thing - the answer in my case was to open the dropdown, then right-click somewhere in it (which opened a second context menu), then take the screenshot. Hitting the screenshot key closed the second context menu, but then took a screenie of my NoScript dropdown 🤓️
Thanks. I'll remember that trick in the future. :-)
With kind regards
A.N. Wilansky
On Sunday 20 April 2025 at 14:34:55 CEST, Matthew (Gliktch) ***@***.***> wrote:
The reason I had to open it in a window was to capture it for you to see. If I try to do so from the pop-up the pop-up disappears when I active a screen capture, that was the only reason. Strictly a practical solution to getting an image to post.
I've noticed the same thing - the answer in my case was to open the dropdown, then right-click somewhere in it (which opened a second context menu), then take the screenshot. Hitting the screenshot key closed the second context menu, but then took a screenie of my NoScript dropdown 🤓️
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***> Gliktch left a comment (hackademix/noscript#431)
The reason I had to open it in a window was to capture it for you to see. If I try to do so from the pop-up the pop-up disappears when I active a screen capture, that was the only reason. Strictly a practical solution to getting an image to post.
I've noticed the same thing - the answer in my case was to open the dropdown, then right-click somewhere in it (which opened a second context menu), then take the screenshot. Hitting the screenshot key closed the second context menu, but then took a screenie of my NoScript dropdown 🤓️
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>