Hi,
I just recently updated (With everyone else) to firefox 57 and noscript 10.1.5.5 with the webextension API.
Now, I not infrequently see the following screen. Notice that there are no domains or names associated with each script permission line:
https://drive.google.com/open?id=1x9RAG ... Rn4hISH9qm
(Sorry for the raw text link, the spam filter kept triggering and not letting me make that a URL)
How do I debug this and continue to use noscript, please?
-- Pat
[UNRELATED] firefox 57 noscript 10.1.5.5 bug report
-
pspinler
[UNRELATED] firefox 57 noscript 10.1.5.5 bug report
Last edited by Thrawn on Thu Dec 07, 2017 11:05 pm, edited 1 time in total.
Reason: Resolved - unrelated
Reason: Resolved - unrelated
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:57.0) Gecko/20100101 Firefox/57.0
-
pspinler
Re: firefox 57 noscript 10.1.5.5 bug report
Apologies for the premature post. I think I just figured this out.
This happens for me when my addressbar compresses the various add-on icons/menus into a single drop down, and I have to select that drop down to get to the noscript dialog.
Then, the portion of the noscript dialog corresponding to the add-on drop down is obscured, as though the add-on drop down is on top of the add-on's dialog. It just so happens that it obscures the domain / host portion of the noscript dialog.
I noticed this also happen with another add-on, and that was the clue I needed to make the association above.
Also, this this does effect multiple add-ons, it appears to be a firefox bug, rather than a noscript issue.
Thanks again, and hopefully this isn't too confusing.
-- Pat
This happens for me when my addressbar compresses the various add-on icons/menus into a single drop down, and I have to select that drop down to get to the noscript dialog.
Then, the portion of the noscript dialog corresponding to the add-on drop down is obscured, as though the add-on drop down is on top of the add-on's dialog. It just so happens that it obscures the domain / host portion of the noscript dialog.
I noticed this also happen with another add-on, and that was the clue I needed to make the association above.
Also, this this does effect multiple add-ons, it appears to be a firefox bug, rather than a noscript issue.
Thanks again, and hopefully this isn't too confusing.
-- Pat
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:57.0) Gecko/20100101 Firefox/57.0