[Fixed] Problem after updating to Firefox 60

Ask for help about NoScript, no registration needed to post
bo elam
Senior Member
Posts: 188
Joined: Sat Oct 14, 2017 2:25 am

[Fixed] Problem after updating to Firefox 60

Post by bo elam » Thu May 10, 2018 5:12 am

There are only 2 programs I update as soon as an update is available, NoScript and Sandboxie (and use their betas). But anyway, today I updated Firefox to 60 after it came out. Everything is fine but I found one little problem and it has to do with NoScript and one of my favorite sites (wildersecurity.com). This is the issue: I can log on but I cant write replies when NoScript is Enabled.

When I first encountered the issue, I was using my W10. So, afterward I also updated Firefox in my W7 and found same issue. To me that was strange. Then I did all kind of test, including creating a new Firefox profile, and without changing anything in Firefox, I installed NoScript and changed nothing in NoScript other than add wilderssecurity.com to the white list. I did not import my settings backup. The result was the same in both of my computers. I still couldnt write replies. I use the beta but in the test with the new profile, I used both, 10.1.8.1 and the latest NS beta.

I logged in other forums and wrote replies without issue. Also wrote emails using web mail. And havent found any issue using NoScript in really complicated sites but I have this issue in a very simple site. So, Giorgio, Barbaz, perhaps this problem I am having is a tell tale sign of something that can happen in some sites after Firefox 60. I posted about the issue at Wilders, perhaps you like to read the thread. One of the moderators who use NoScript is not experiencing the issue. Here is the link to the thread and I ll post a couple of pictures.
https://www.wilderssecurity.com/threads ... 60.403578/

In the first one, NoScript is disabled. You can see the cursor at the extreme left of the box at the bottom. Ready to start writing. Also, the functions (Bold, Italic, etc) are there. In the second picture, NoScript is enabled and wilderssecurity is allowed and my browser is over the box, but even so, the cursor doesn't appear, I cant write nothing. And the functions on top of the box are not there.

Image


Image

Bo
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0

barbaz
Senior Member
Posts: 9230
Joined: Sat Aug 03, 2013 5:45 pm

Re: Problem after updating to Firefox 60

Post by barbaz » Thu May 10, 2018 4:35 pm

When this issue occurs, do you see anything related in the Browser Console? (Ctrl-Shift-J)
(if you don't know what's related, turn off CSS warnings and post everything else you see)
*Always* check the changelogs BEFORE updating that important software!
-

bo elam
Senior Member
Posts: 188
Joined: Sat Oct 14, 2017 2:25 am

Re: Problem after updating to Firefox 60

Post by bo elam » Thu May 10, 2018 7:48 pm

Barbaz, I am not familiar with the Browser console and the output. I unticked all 3 items under CSS (I am not sure if that's what you suggested). And ticked everything else for the rest. This is some of what I saw.

"Handler function DebuggerProgressListener.prototype.onStateChange threw an exception: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIWebProgress.DOMWindow]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js :: _docShellToWindow :: line 768" data: no]
Stack: _docShellToWindow@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:768:9
_docShellsToWindows/<@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:792:38
_docShellsToWindows@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:792:12
_notifyDocShellsUpdate@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:796:19
DebuggerProgressListener.prototype.onStateChange<@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:1624:7
exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
Line: 768, column: 0" ThreadSafeDevToolsUtils.js:88:5
"Handler function DebuggerProgressListener.prototype.onStateChange threw an exception: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIWebProgress.DOMWindow]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js :: DebuggerProgressListener.prototype.onStateChange< :: line 1627" data: no]
Stack: DebuggerProgressListener.prototype.onStateChange<@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:1627:9
exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
Line: 1627, column: 0"


Bo
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0

bo elam
Senior Member
Posts: 188
Joined: Sat Oct 14, 2017 2:25 am

Re: Problem after updating to Firefox 60

Post by bo elam » Thu May 10, 2018 8:19 pm

Barbaz, I just went again to Wilders, after opening the console and unticking items in CSS, for a few moments the function to write worked, this is what appeared in the console afterward:

1525982997684 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232} WARN Please specify whether you want browser_style or not in your browser_action options.
Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xul
WebGL Hook webglHook.js:1:1
XenForo.activate( [object HTMLDocument] )xenforo.js:226
Attachments changed, total files: 0, images: 0 attachment_editor_new.js:15:291
XenForo.init() 186ms. jQuery 1.11.0/1.2.8-dev


And then after moving around the forum, the writing posts function did not work anymore, and the console generated this output:

"Handler function DebuggerProgressListener.prototype.onStateChange threw an exception: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIWebProgress.DOMWindow]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js :: _docShellToWindow :: line 768" data: no]
Stack: _docShellToWindow@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:768:9
_docShellsToWindows/<@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:792:38
_docShellsToWindows@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:792:12
_notifyDocShellsUpdate@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:796:19
DebuggerProgressListener.prototype.onStateChange<@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:1624:7
exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
Line: 768, column: 0" ThreadSafeDevToolsUtils.js:88:5
"Handler function DebuggerProgressListener.prototype.onStateChange threw an exception: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIWebProgress.DOMWindow]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js :: DebuggerProgressListener.prototype.onStateChange< :: line 1627" data: no]
Stack: DebuggerProgressListener.prototype.onStateChange<@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/tab.js:1627:9
exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
Line: 1627, column: 0" ThreadSafeDevToolsUtils.js:88:5
Promise rejected after context unloaded: Message manager disconnected

Bo
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0

User avatar
therube
Ambassador
Posts: 7431
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: Problem after updating to Firefox 60

Post by therube » Fri May 11, 2018 3:42 am

Confirmed.

FF 60
NoScript 10.1.8.1

(I must say, I'm confused - by NoScript...)


Allow & Temp-Allow do not allow ( ;-)) typing into the Reply box, nor does the reply box display its editing controls (as pictured above).

The only way I see to get things allowed, is to 'Set all on this page to Temporarily TRUSTED'.
(Not even Allow Globally works.)

But...

If …wilderssecurity.com (hey, look at that, you can actually copy from the dropdown dialog box, imagine that) is already Allowed or Temp-Allowed, (or if you are running Allow Globally), 'Set all on this page' does nothing, so you have to Revoke those permissions first & then 'Set all' at which point things work.


(Did I say confused?)

The NoScript icon, an S with an ! on its end, S! ?
Somehow, now, every page is showing that?
(And I have no idea what it is even supposed to mean?)
(And it persists a restart, reloading from Session Restore.)
I think I must be stuck in some sort of Allow Global mode, because I'm getting no count of domains?


Console, it all looks like noise to me (but then I've never been good with FF's version & always found it a pain to use).

Code: Select all

[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] apply <unavailable>  log.js:9:39
[NoScript] Including /ui/ui.css  log.js:9:39
[NoScript] Including /lib/punycode.js  log.js:9:39
[NoScript] Including /lib/tld.js  log.js:9:39
[NoScript] Including /common/Policy.js  log.js:9:39
[NoScript] Cannot collect noscript activity data <unavailable> Could not establish connection. Receiving end does not exist. collectSeen@moz-extension://8756aa82-59cb-465a-bfd5-b6863ad6060c/bg/main.js:265:38
  log.js:12:5
[NoScript] Cannot collect noscript activity data <unavailable> Could not establish connection. Receiving end does not exist. collectSeen@moz-extension://8756aa82-59cb-465a-bfd5-b6863ad6060c/bg/main.js:265:38
  log.js:12:5

Can't comment on other FF &/or NoScript versions.
(Profile wasn't quit clean, & I do have a anti-coin-miner extension in there...)


Image

https://s25.postimg.cc/74ke64y33/No_Scr ... _sorts.png


With SeaMonkey 2.49.3 & NoScript 5 (my hacked version), I have no issues.
I can log in, & reply without allowing anything.
In that mode, I don't have the reply-box editing controls, but that is expected.
Allow, in any form, wilderssecurity.com & then I'll have my controls.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 Lightning/5.4

bo elam
Senior Member
Posts: 188
Joined: Sat Oct 14, 2017 2:25 am

Re: Problem after updating to Firefox 60

Post by bo elam » Fri May 11, 2018 3:56 am

therube wrote:Confirmed.

FF 60
NoScript 10.1.8.1
Thanks, therube. :)

I cant figure how to fix this. If using a new profile would do it, for Wilders, I happily do it. I tested with a few, and nothing good has come out. A few minutes ago, I created a new profile again, and same result. Only change I made before installing NoScript 10.1.8.1 and allowing wilderssecurity.com was enable Menu bar, I tested without Sandboxie or any other addonr installed.

Image

Bo
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0

User avatar
therube
Ambassador
Posts: 7431
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: Problem after updating to Firefox 60

Post by therube » Fri May 11, 2018 4:31 am

New Profile makes no difference.
Having a "better" understanding of NoScript icons & hieroglyphs makes no difference.

So from what I can see, on Wilders, for each & every Wilders tab, you have to first Revoke permissions, then 'Set all this page'.
(And if wilders is Allowed, you have to first change it to something like Temp-Allow, before you can revoke...)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 Lightning/5.4

User avatar
Giorgio Maone
Site Admin
Posts: 8716
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Problem after updating to Firefox 60

Post by Giorgio Maone » Fri May 11, 2018 5:41 am

therube wrote: The NoScript icon, an S with an ! on its end, S! ?
Somehow, now, every page is showing that?
(And I have no idea what it is even supposed to mean?)
(And it persists a restart, reloading from Session Restore.)
It means that you've used "Disable restrictions globally" (for every page), i.e. NoScript won't enforce any restriction, even the presets (DEFAULT, TRUSTED, UNTRUSTED and CUSTOM) are still assigned, but not respected until you switch back to "Enable restrictions globally".
therube wrote: I think I must be stuck in some sort of Allow Global mode, because I'm getting no count of domains?
Yes, it is an "Allow global" mode (no restrictions applied). Why stuck? Doesn't "Enable restrictions globally" work for you?

Also, could somehow please restate the main problem? I'm quite confused as well :)
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

bo elam
Senior Member
Posts: 188
Joined: Sat Oct 14, 2017 2:25 am

Re: Problem after updating to Firefox 60

Post by bo elam » Fri May 11, 2018 5:54 am

Giorgio Maone wrote: Also, could somehow please restate the main problem? I'm quite confused as well :)
Giorgio, in short, the problem is I cant write replies at Wilders after updating to Firefox 60. I reproduce the problem in my 2 systems, W7 and W10 with my current profiles or with new Firefox profiles. Please look at the 2 pictures in the opening post. In the one on top, I can write replies after disabling NoScript. In the 2nd picture, with NoScript enabled and wilderssecurity.com being allowed, I cant write replies. Look at the bottom of both pictures so you can compare and see the difference. In the picture on top, the block where you write is complete. In the picture at the bottom, the block where you write is empty, cant write nothing. :)

Bo
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0

User avatar
therube
Ambassador
Posts: 7431
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: Problem after updating to Firefox 60

Post by therube » Fri May 11, 2018 1:15 pm

The problem is that Wilders (forum Reply dialogs) & FF & NoScript do not work - unless you enable, 'Set all on this page to Temporarily TRUSTED' (& then you have to do it for each Wilders tab, at that).
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 Lightning/5.4

User avatar
Giorgio Maone
Site Admin
Posts: 8716
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Problem after updating to Firefox 60

Post by Giorgio Maone » Fri May 11, 2018 1:22 pm

I managed to reproduce it, but only intermittently (by trying each time on a new profile).
And as soon as the page starts working, with ...wildersecurity.com set as TRUSTED, it doesn't stop anymore, so it's quite difficult to pin down.
Currently I'm trying to figure out what's the difference between "before" and "after" it starts working.
All I can say is that when it doesnt' work, an error message from the WebExtensions API's implementation guts ("TypeError: this.contentWindow is null ExtensionPageChild.jsm:191:5") always appears in the console before other errors from the comment editor's script, hinting at some Firefox bug...
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

David_L
Posts: 18
Joined: Fri Dec 29, 2017 5:53 pm

Re: Problem after updating to Firefox 60

Post by David_L » Fri May 11, 2018 4:30 pm

Does this issue affect any web sites other than wilderssecurity.com?
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0

bo elam
Senior Member
Posts: 188
Joined: Sat Oct 14, 2017 2:25 am

Re: Problem after updating to Firefox 60

Post by bo elam » Fri May 11, 2018 7:33 pm

David_L wrote:Does this issue affect any web sites other than wilderssecurity.com?
David, other than at Wilders, I haven't encountered the problem in any of the rest of my regulars sites. I posted replies in 3 other forums (including this one) and wrote web mails without any issue.

Bo
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0

barbaz
Senior Member
Posts: 9230
Joined: Sat Aug 03, 2013 5:45 pm

Re: Problem after updating to Firefox 60

Post by barbaz » Mon May 14, 2018 2:19 am

Split the unrelated generic feedback & replies to https://forums.informaction.com/viewtop ... 24&t=24746 .
*Always* check the changelogs BEFORE updating that important software!
-

skriptimaahinen
Senior Member
Posts: 161
Joined: Wed Jan 10, 2018 7:37 am

Re: Problem after updating to Firefox 60

Post by skriptimaahinen » Tue May 22, 2018 9:22 am

Well sh**. Looks like the culprit is the same bug as with the blank page not refreshing (https://forums.informaction.com/viewtop ... 10&t=24752). Definitely not NS bug, as I can reproduce both problems with minimal test webextension:

Code: Select all

manifest.json:
{
    "manifest_version": 2,
    "name": "Content CSS Test",
    "version": "1.0",
    "description": "Breaking FF60 blank page refresh with content CSS.",
    "applications": {
        "gecko": {
            "id": "addon@example.com",
            "strict_min_version": "60.0"
        }
    },
    "permissions": [
        "<all_urls>"
    ],
    "content_scripts": [
        {
            "run_at": "document_start",
            "matches": ["<all_urls>"],
            "match_about_blank": true,
            "all_frames": true,
            "css": [
                "content.css"
            ]
        }
    ]
}
Where content.css can be empty file and all_frames is optional depending on what frames you want to break.

Why having developer tools open (either console or toolbar) fixes the problem for the wilderssecurity, but not for the about:blank is beyond me though.

However, thinking a bit harder, I came up with a workaround for NS that does not seem to have adverse effects:

Code: Select all

manifest.json:
...
"content_scripts": [
  {
    "run_at": "document_start",
    "matches": ["<all_urls>"],
    "match_about_blank": true,
    "all_frames": true,
    "js": [
      "lib/log.js",
      "content/onScriptDisabled.js",
      "content/content.js",
      "content/PlaceHolder.js"
    ]

  },
  {
    "matches": ["<all_urls>"],
    "match_about_blank": true,
    "all_frames": true,
    "css": [
      "/content/content.css"
    ]
  }
],
...
Maybe this is warranted after all, unless Giorgio has something else cooked up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0

Post Reply