Page 2 of 2

Re: "Temporally allow top-level domain by default" doesn't w

Posted: Tue Dec 20, 2016 4:06 pm
by barbaz
You're welcome.

Re: [Closed] "Temp-allow top-level domain by default" fails

Posted: Thu Jan 12, 2017 3:55 am
by cye3s
Same here, and I am using zh-CN locale, and I need to refresh page to temporally allow top-level domain.
Disable all other addons, did not work.
Export NS setting, reset prefs.js file, import NS setting, did not work.
Rollback to 2.9.5.1, works fine.
I create an empey profile, only install NS 2.9.5.2, works fine, very weird.

So I am using 2.9.5.1 now.

Re: [Closed] "Temp-allow top-level domain by default" fails

Posted: Thu Jan 12, 2017 5:38 pm
by barbaz
cye3s, did you try Standard Diagnostic (leaving NoScript enabled) on your main profile?

Re: [Closed] "Temp-allow top-level domain by default" fails

Posted: Fri Jan 13, 2017 2:25 am
by cye3s
barbaz wrote:cye3s, did you try Standard Diagnostic (leaving NoScript enabled) on your main profile?
Yes, I tried.
Now I can reproduce the problem on brand new profile on Firefox 45.6.0 ESR 32bit(zh-CN version)
https://download.mozilla.org/?product=f ... lang=zh-CN

I upload the test profile to Mega, please try it, hope this profile can help you to reproduce the problem, thanks!

https://mega.nz/#!yp4TkJBS!lLW8l2jgrZlt ... 6SjtkGeF8M

1.Unzip test_profile.zip
2.run firefox.exe -p and point to test_profile
3.click cnbeta.com on bookmark toolbar

Re: [Closed] "Temp-allow top-level domain by default" fails

Posted: Fri Jan 13, 2017 2:30 am
by barbaz
@cye3s Remember to log in before posting so that you can work with your posts more easily and don't need to solve the CAPTCHA every time. (I've fixed your last post.)

The mega.nz download link does not work for me. I just get a blank page with a grey circle in the middle.

Re: [Closed] "Temp-allow top-level domain by default" fails

Posted: Fri Jan 13, 2017 2:36 am
by cye3s
barbaz wrote:@cye3s Remember to log in before posting so that you can work with your posts more easily and don't need to solve the CAPTCHA every time. (I've fixed your last post.)

The mega.nz download link does not work for me. I just get a blank page with a grey circle in the middle.
I put it on Google driver
https://drive.google.com/open?id=0B-Xv9 ... XR1VU90UnM

Re: [Closed] "Temp-allow top-level domain by default" fails

Posted: Fri Jan 13, 2017 2:37 am
by barbaz
Got it, thanks. Testing shortly...

EDIT I confirm the wrong behavior with that profile. I'll try to troubleshoot it, most likely tomorrow.

Re: [Closed] "Temp-allow top-level domain by default" fails

Posted: Fri Jan 13, 2017 3:11 am
by cye3s
barbaz wrote:Got it, thanks. Testing shortly...

EDIT I confirm the wrong behavior with that profile. I'll try to troubleshoot it, most likely tomorrow.
Good to know :P

Re: "Temp-allow top-level domain by default" fails

Posted: Fri Jan 13, 2017 3:20 am
by barbaz
Actually I think I've already ferreted this one out.

Apparently the culprit is that you've got ABE disabled. So go to NoScript Options > Advanced > ABE, and check "Enable ABE". Does it work then?

Re: "Temp-allow top-level domain by default" fails

Posted: Fri Jan 13, 2017 3:33 am
by cye3s
barbaz wrote:Actually I think I've already ferreted this one out.

Apparently the culprit is that you've got ABE disabled. So go to NoScript Options > Advanced > ABE, and check "Enable ABE". Does it work then?
No, not work here. Did you restart firefox after Enable ABE?
First time you open bookmark after run firefox, behavior wrong, then close the tab, reopen that bookmark or just refresh the tab, both behavior normal.
So this wrong behavior only happend on the first time some bookmark or URL is open.

And even I disable ABE, this setting sould work, right(works on 2.9.5.1)? ;)

Re: "Temp-allow top-level domain by default" fails

Posted: Fri Jan 13, 2017 3:46 am
by barbaz
I was editing prefs.js by hand with the browser closed. I was also starting the browser only in a sandbox, to ensure that it started from the exact same baseline profile each time.

Once I discovered that disabling ABE was the culprit, I tried it on my main profile through the GUI, and reproduced this problem there too.


After re-enabling ABE, try quitting Firefox, then starting Firefox from Command Prompt with the -purgecaches command-line switch.
https://developer.mozilla.org/docs/Mozi ... ne_Options
cye3s wrote:And even I disable ABE, this setting sould work, right(works on 2.9.5.1)? ;)
I would guess so, but I'm not sure. ABE does, by design, handle more than just the application boundary enforcing.