New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoSquint 2.1.8 sporadically stops functioning #73

Closed
neil49 opened this Issue Apr 10, 2013 · 35 comments

Comments

Projects
None yet
5 participants
@neil49
Copy link

neil49 commented Apr 10, 2013

After a day of running without problems, No Squint failed again when opening my Gmail page.

After closing Firefox 20 and restarting it, No Squint operates normally. For now.

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 10, 2013

What does "failed" mean?

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 10, 2013

From my end, it means that it no longer remembers site settings, shows
"N/A" next to magnifier icon, refuses to save settings and close settings
control panel after clicking on "OK", randomly and not resulting from any
changes that I'm aware of. See previous reports via Add-on reviews in
Firefox.

On Wed, Apr 10, 2013 at 11:42 AM, Jason Tackaberry <notifications@github.com

wrote:

What does "failed" mean?


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16186343
.

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 10, 2013

Yes, the previous addon reviews are quite lacking in detail and not remotely helpful. Finally someone has bothered to submit a bug report about this so I'm very curious to get more details to understand what is happening.

The next time this happens, can you open Tools | Web Developer | Error Console, click the Errors button at the top of the console window, and see if there are any errors related to NoSquint there? If so, can you copy/paste them here? Thanks.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 10, 2013

Okay, I just experienced the problem again. When I followed your
instructions, I did get some error notices, but when I closed that page and
reopened it after reading your instructions again, the list of errors was
gone. I DID see at least a few that had NS or something, which I guess
stands for No Squint, but I'll have to get back with the copy and paste
next time I see them

Keep in mind I know NOTHING about any of this, so you'll have to bear with
me.

Neil

On Wed, Apr 10, 2013 at 11:53 AM, Jason Tackaberry <notifications@github.com

wrote:

Yes, the previous addon reviews are quite lacking in detail and not
remotely helpful. Finally someone has bothered to submit a bug report about
this so I'm very curious to get more details to understand what is
happening.

The next time this happens, can you open Tools | Web Developer | Error
Console, click the Errors button at the top of the console window, and see
if there are any errors related to NoSquint there? If so, can you
copy/paste them here? Thanks.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16186988
.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 10, 2013

Here are three error reports for three different Web sites just generated
after No Squint went int its dydfunctional mode and before I closed the
browser and reopened it. I'm now going to close Firefox and reopen. Stand
by.

Timestamp: 4/10/2013 2:33:04 PM
Error: NS_NOINTERFACE: Component returned failure code: 0x80004002
(NS_NOINTERFACE) [nsIInterfaceRequestor.getInterface]
Source File: resource://gre/modules/PrivateBrowsingUtils.jsm
Line: 25

Timestamp: 4/10/2013 2:34:58 PM
Error: NS_NOINTERFACE: Component returned failure code: 0x80004002
(NS_NOINTERFACE) [nsIInterfaceRequestor.getInterface]
Source File: resource://gre/modules/PrivateBrowsingUtils.jsm
Line: 25

Timestamp: 4/10/2013 2:37:30 PM
Error: NS_NOINTERFACE: Component returned failure code: 0x80004002
(NS_NOINTERFACE) [nsIInterfaceRequestor.getInterface]
Source File: resource://gre/modules/PrivateBrowsingUtils.jsm
Line: 25

On Wed, Apr 10, 2013 at 11:53 AM, Jason Tackaberry <notifications@github.com

wrote:

Yes, the previous addon reviews are quite lacking in detail and not
remotely helpful. Finally someone has bothered to submit a bug report about
this so I'm very curious to get more details to understand what is
happening.

The next time this happens, can you open Tools | Web Developer | Error
Console, click the Errors button at the top of the console window, and see
if there are any errors related to NoSquint there? If so, can you
copy/paste them here? Thanks.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16186988
.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 10, 2013

Hi,

Okay, I've just closed and restarted Firefox and No Squint is back running
correctly. I just went to the same three Web sites that generated the error
reports in my email sent just before this one.

On Wed, Apr 10, 2013 at 11:53 AM, Jason Tackaberry <notifications@github.com

wrote:

Yes, the previous addon reviews are quite lacking in detail and not
remotely helpful. Finally someone has bothered to submit a bug report about
this so I'm very curious to get more details to understand what is
happening.

The next time this happens, can you open Tools | Web Developer | Error
Console, click the Errors button at the top of the console window, and see
if there are any errors related to NoSquint there? If so, can you
copy/paste them here? Thanks.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16186988
.

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 10, 2013

NS isn't NoSquint in this case (unfortunately!). If you see any errors that say 'nosquint' in the Source File URI, that's NoSquint.

Are you running in Private Browsing mode by default?

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 10, 2013

Oh, well--things are never as simple as they seem. I checked Options>
Privacy, and the "Always use private browsing mode" box is UNchecked.
That's all I can tell you about THAT. Would there be somewhere else to look
for the status of Private Browsing?

Where is the "Source File URI"? Is it in this line, taken from one of the
error reports I just sent you?:

Source File: resource://gre/modules/
PrivateBrowsingUtils.jsm

On Wed, Apr 10, 2013 at 3:16 PM, Jason Tackaberry
notifications@github.comwrote:

NS isn't NoSquint in this case (unfortunately!). If you see any errors
that say 'nosquint' in the Source File URI, that's NoSquint.

Are you running in Private Browsing mode by default?


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16199097
.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 10, 2013

Whoaaa!

I just realized you referred to NoSquint 2.1. EIGHT in your subject line. I
was using 2.1.SEVEN, which I thought was the most recent version. Do you
think that will make any difference re my current problems? I've just
removed .7 and installed .8, so what do you think I should expect?

Neil

On Wed, Apr 10, 2013 at 3:16 PM, Jason Tackaberry
notifications@github.comwrote:

NS isn't NoSquint in this case (unfortunately!). If you see any errors
that say 'nosquint' in the Source File URI, that's NoSquint.

Are you running in Private Browsing mode by default?


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16199097
.

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 10, 2013

No it's not likely to make a difference, unfortunately. The change in 2.1.8 was very minor and not a bug fix.

Source File URI is that Source File line you quoted, right. If that says something like chrome://nosquint/[...] then this is a bug within NoSquint's code.

The reference to PrivateBrowsingUtils.jsm is interesting though, and could be related. Do these errors show up every time you restart Firefox? Do they occur if NoSquint is disabled?

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 10, 2013

Just to be clear, the errors only seem to show up in the Web
Developer>Error Console AFTER No Squint has "failed", a Web site displays
in the default (I assume) 100% level, and I open the Error Console and
check. As I've never opened the Error Console until today, per your
instructions, It's been my only experience.

I just opened the Console now, with No Squint running okay, and there are
no error reports, so I'll have to check next time No Squint crashes. I
guess I'll check periodically anyway, just to see if anything appears. As I
mentioned earlier, it SEEMS that once the Error Console closes, any notices
that were there disappear.

I just disabled NoSquint, and there were a couple of error notices with the
word "chrome" at the beginning, but no mention of NoSquint or Private
Browsing. What does "chrome" mean? Is that a reference to the browser? I
have that browser installed, but my default setting is Mozilla Firefox.

On Wed, Apr 10, 2013 at 3:52 PM, Jason Tackaberry
notifications@github.comwrote:

No it's not likely to make a difference, unfortunately. The change in
2.1.8 was very minor and not a bug fix.

Source File URI is that Source File line you quoted, right. If that says
something like chrome://nosquint/[...] then this is a bug within NoSquint's
code.

The reference to PrivateBrowsingUtils.jsm is interesting though, and could
be related. Do these errors show up every time you restart Firefox? Do they
occur if NoSquint is disabled?


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16201292
.

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 10, 2013

This might help in pinning down the problem.

I run Mac OS X (10.8.3) on an early 2008 iMac.

As described above in this thread, the OK button ceased to work with NoSquint 2.1.8 and Firefox 20.0, as did the Return key with NoSquint. I've also had problems with NoSquint forgetting its settings. This isn't consistent, though — I can't discern a pattern. But when I quit Firefox and restarted it, the problem page was OK again. As I recall, the OK button might work once. But after that, no dice.

I then disabled all the other extensions, but the OK button still did nothing. Nevertheless, I trashed everything Mozilla & Firefox in the entire system and using Safari downloaded Firefox 20.0 again.

I opened it and without making any changes whatsoever other than typing in the URL to NoSquint 2.1.8, I installed it. After bumping up the page type, I clicked on the Zooming tab and made a couple of changes. I clicked on the OK button, but again nothing happened. I dismissed NoSquint by clicking the close button. So all that was running in Firefox was NoSquint.

I trashed all of Firefox 20.0 again and went back to 19.0.2 because the higher-visibility Aeon 6 theme is causing a problem, too. It's disabled in Firefox 20.0, though not if I turn off version checking. But turning that off might further complicate the NoSquint issue in all the prefs.js settings, and I might not know what to do next to straighten that all out. Firefox 19.0.2 takes care of the immediate problem, and I could start again with 20.0 later.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 11, 2013

Okay, I couldn't understand about half of that (not your fault), but I've
just reverted to Firefox 19.0.2, which will only accept NoSquint
2.1.6--nothing newer. Is this what you have found? I'm sceered of all them
warnings about older versions of Add-ons. Should I be?

On Wed, Apr 10, 2013 at 6:11 PM, Hyperoptic notifications@github.comwrote:

This might help in pinning down the problem.

I run Mac OS X (10.8.3) on an early 2008 iMac.

As described above in this thread, the OK button ceased to work with
NoSquint 2.1.8 and Firefox 20.0, as did the Return key with NoSquint. I've
also had problems with NoSquint forgetting its settings. This isn't
consistent, though — I can't discern a pattern. But when I quit Firefox and
restarted it, the problem page was OK again. As I recall, the OK button
might work once. But after that, no dice.

I then disabled all the other extensions, but the OK button still did
nothing. Nevertheless, I trashed everything Mozilla & Firefox in the entire
system and using Safari downloaded Firefox 20.0 again.

I opened it and without making any changes whatsoever other than typing in
the URL to NoSquint 2.1.8, I installed it. After bumping up the page type,
I clicked on the Zooming tab and made a couple of changes. I clicked on the
OK button, but again nothing happened. I dismissed NoSquint by clicking the
close button. So all that was running in Firefox was NoSquint.

I trashed all of Firefox 20.0 again and went back to 19.0.2 because the
higher-visibility Aeon 6 theme is causing a problem, too. It's disabled in
Firefox 20.0, though not if I turn off version checking. But turning that
off might further complicate the NoSquint issue in all the prefs.js
settings, and I might not know what to do next to straighten that all out.
Firefox 19.0.2 takes care of the immediate problem, and I could start again
with 20.0 later.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16208187
.

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 11, 2013

If you are asking me, not jtackaberry, NoSquint 2.1.6 is contemporary with Firefox 19.0.2, so all should be well with both. When, using Firefox 19.0.2, I check my add-ons manually for updates, the newer NoSquint 2.1.8 isn't offered, so Firefox 19.0.2 and NoSquint 2.1.6 is a match made in heaven.

I am no programmer, but I don't think there would be a danger running any even older NoSquint than 2.1.6. It doesn't handle any security operations, just type and graphic sizes. I don't know if an older one would even load, though.

I'm not certain, but I don't think Firefox 20.0 has any security upgrades over Firefox 19.0.2, just usability changes you probably wouldn't notice. I hadn't. When I looked for Mozilla's notes on Firefox 20.0, the only ones I could find were on Firefox 20.0 nightlies, the versions offered to developers each night.

One site mentioned that the complete notes on 20.0 for regular users hadn't been completed. So if 19.0.2 had security concerns, that certainly would have been mentioned, I suspect.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 11, 2013

I guess I was asking you, since I was responding to your message as it
appeared in my Inbox.

Anyway, I just noticed upon startup today that Firefox has updated itself
to 20.0 again, even though I had disabled automatic updating in favor of
checking only. So much for that.

I'll leave 20.0 in place and see how long NoSquint 2.1.6 continues to
function properly; however, I thought that when I reverted to 2.1.6, I saw
a notation that Firefox 20 wouldn't accept NS 2.1.6. (?).

Thanks

On Thu, Apr 11, 2013 at 1:05 AM, Hyperoptic notifications@github.comwrote:

If you are asking me, not jtackaberry, NoSquint 2.1.6 is contemporary with
Firefox 19.0.2, so all should be well with both. When, using Firefox
19.0.2, I check my add-ons manually for updates, the newer NoSquint 2.1.8
isn't offered, so Firefox 19.0.2 and NoSquint 2.1.6 is a match made in
heaven.

I am no programmer, but I don't think there would be a danger running any
even older NoSquint than 2.1.6. It doesn't handle any security operations,
just type and graphic sizes. I don't know if an older one would even load,
though.

I'm not certain, but I don't think Firefox 20.0 has any security upgrades
over Firefox 19.0.2, just usability changes you probably wouldn't notice. I
hadn't. When I looked for Mozilla's notes on Firefox 20.0, the only ones I
could find were on Firefox 20.0 nightlies, the versions offered to
developers each night.

One site mentioned that the complete notes on 20.0 for regular users
hadn't been completed. So if 19.0.2 had security concerns, that certainly
would have been mentioned, I suspect.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16218221
.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 11, 2013

Hi,

NoSquint 2.1.6 just started acting up with Firefox 20. When clicking on
Add-on toolbar to bring up NoSquint menu, clicking on "Site Settings" no
longer brings up control panel. +/- buttons at top of page still effect
changes as commanded, and percentage number in Add-on bar changes as well.

Now I'm going to try and go back to Firefox 19.0.2, and hope it doesn't get
auto-updated again, despite my settings in Options>Update.

Timestamp: 4/11/2013 3:12:47 PM
Error: TypeError: browser.markupDocumentViewer is undefined
Source File: chrome://nosquint/content/browser.js
Line: 466

Timestamp: 4/11/2013 3:12:48 PM
Error: TypeError: browser.markupDocumentViewer is undefined
Source File: chrome://nosquint/content/browser.js
Line: 466

Timestamp: 4/11/2013 3:12:48 PM
Error: TypeError: browser.markupDocumentViewer is undefined
Source File: chrome://nosquint/content/browser.js
Line: 466

Timestamp: 4/11/2013 3:12:48 PM
Error: TypeError: browser.markupDocumentViewer is undefined
Source File: chrome://nosquint/content/browser.js
Line: 466

Timestamp: 4/11/2013 3:12:51 PM
Error: TypeError: browser.markupDocumentViewer is undefined
Source File: chrome://nosquint/content/browser.js
Line: 466

Timestamp: 4/11/2013 3:12:54 PM
Error: TypeError: browser.markupDocumentViewer is undefined
Source File: chrome://nosquint/content/browser.js
Line: 466

Timestamp: 4/11/2013 3:12:55 PM
Error: TypeError: browser.getUserData(...) is null
Source File: chrome://nosquint/content/browser.js
Line: 386

Timestamp: 4/11/2013 3:13:19 PM
Error: TypeError: browser.getUserData(...) is null
Source File: chrome://nosquint/content/browser.js
Line: 386

Timestamp: 4/11/2013 3:13:23 PM
Error: TypeError: browser.getUserData(...) is null
Source File: chrome://nosquint/content/browser.js
Line: 386

Timestamp: 4/11/2013 3:13:27 PM
Error: TypeError: browser.getUserData(...) is null
Source File: chrome://nosquint/content/browser.js
Line: 386

Timestamp: 4/11/2013 3:13:36 PM
Error: TypeError: browser.getUserData(...) is null
Source File: chrome://nosquint/content/browser.js
Line: 386

On Wed, Apr 10, 2013 at 3:52 PM, Jason Tackaberry
notifications@github.comwrote:

No it's not likely to make a difference, unfortunately. The change in
2.1.8 was very minor and not a bug fix.

Source File URI is that Source File line you quoted, right. If that says
something like chrome://nosquint/[...] then this is a bug within NoSquint's
code.

The reference to PrivateBrowsingUtils.jsm is interesting though, and could
be related. Do these errors show up every time you restart Firefox? Do they
occur if NoSquint is disabled?


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16201292
.

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 11, 2013

By supplying an email address when registering here, everyone receives an email from everyone else who posts in this thread.

You can stop the auto updates dead in their tracks by going to Firefox's address bar and typing "about:config" without the quotation marks and without spaces. Then press the Return key.

A warning window will appear. Click I'll be Careful (or whatever it may say) to dismiss it.

What you've opened is Firefox's foundation of options and preferences. Ignore that laundry list of confusion because you are going to isolate only two.

Where it says Search: type or paste this into the blank:
app.update.auto

Two preferences only will appear. Look to the right, to the small heading Value. Double click one or both of these settings that may have true under the heading Value. This will change true to false.

Go back up to Search and delete app.update.auto, that you had just typed in or pasted. Type or paste this into the blank:
app.update.autoUpdateEnabled

If that one doesn't appear in the preference list, just restart Firefox.

If it does appear and it's Value says true, double-click it so it says false, then restart Firefox.

For the heck of it, check the options to see if automatic updating is still off.

With all those auto updates off in about:config, you can still check for updates manually at the list of add-ons. If there are any updates, you can then choose which to do so one at a time.

When this NoSquint problem is resolved, remember to revert those about:config settings from false to true if you wish to. I leave mine on false because that auto update option is a notorious turkey.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 11, 2013

Hi, just a quick question as I 'm trying to follow your instructions. The
value for the first item was already set to false. The entire line was in
bold type. Does this indicate that it had been changed from the original
setting (via the Tools>Options>Update panel?

I copied and pasted the second item into the search bar, and the field came
up blank. I happened to scan down the list of preferences, and I DID see
this: app.update.enabled (no caps and the words "autoUpdate" omitted), and
its value set at "true", with the entire line in NON-bold type. Is this the
same thing you were referring to?

Otherwise, to recap: I checked the first search item and found the line in
bold and the setting already set to false. Searched for the second item,
found nothing. Closed and restarted Firefox, setting in Options was still
checked to "Check for updates".

So, all that seems unresolved is the matter of the app.update.enabled item

On Thu, Apr 11, 2013 at 6:18 PM, Hyperoptic notifications@github.comwrote:

By supplying an email address when registering here, everyone receives an
email from everyone else who posts in this thread.

You can stop the auto updates dead in their tracks by going to Firefox's
address bar and typing "about:config" without the quotation marks and
without spaces. Then press the Return key.

A warning window will appear. Click I'll be Careful (or whatever it may
say) to dismiss it.

What you've opened is Firefox's foundation of options and preferences.
Ignore that laundry list of confusion because you are going to isolate only
two.

Where it says Search: type or paste this into the blank:
app.update.auto

Two preferences only will appear. Look to the right, to the small heading
Value. Double click one or both of these settings that may have true under
the heading Value. This will change true to false.

Go back up to Search and delete app.update.auto, that you had just typed
in or pasted. Type or paste this into the blank:
app.update.autoUpdateEnabled

If that one doesn't appear in the preference list, just restart Firefox.

If it does appear and it's Value says true, double-click it so it says
false, then restart Firefox.

For the heck of it, check the options to see if automatic updating is
still off.

With all those auto updates off in about:config, you can still check for
updates manually at the list of add-ons. If there are any updates, you can
then choose which to do so one at a time.

When this NoSquint problem is resolved, remember to revert those
about:config settings from false to true if you wish to. I leave mine on
false because that auto update option is a notorious turkey.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16267651
.

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 12, 2013

< The value for the first item was already set to false. The entire line was in bold type. Does this indicate that it had been changed from the original setting (via the Tools>Options>Update panel?>

Yes

< I DID see this: app.update.enabled (no caps and the words "autoUpdate" omitted), and its value set at "true", with the entire line in NON-bold type. Is this the same thing you were referring to?>

Yes. Maybe my notes editor added the extra as a "correction." I can't explain it otherwise. Any missing entry in about:config in your version as opposed to mine may be because I have a document in Firefox's Profiles folder called user.js where I make about:config changes. It links to about:config and is easier to handle. The document needs occasional updating. It goes back years, but I keep on top of it. As well, I have a Mac, as I mentioned in a previous post, so perhaps the entries are different in Windows.

You might check out this site to clear up some questions.

http://kb.mozillazine.org/Firefox_:_FAQs_:_About:config_Entries

Mozillazine, a group of volunteers, is not affiliated with Mozilla. The link above goes to the about:config page in the Mozillazine Knowledge Base. The updating options, at least most of them, depending on the age of that article, are there.

Mozillazine also a question-and-answer forum that goes back years:

http://forums.mozillazine.org/index.php

If you go to it but it says you are banned, it's because of a forum software bug. The ban notice includes a couple of lines saying to clear the cache and the cookies, and try again. Apparently you're never banned if you've signed up and log in. (I have nothing to do with that forum.)

But all this may be moot. I have since gone back to using Firefox 20.0. I downloaded the add-on checkCompatibility that turns off old add-on checking. I then downloaded NoSquint 2.1.6, and with compatibility checking turned off, it works in 20.0. 2.1.6 is here:

https://addons.mozilla.org/en-US/firefox/addon/nosquint/versions/

Scroll down a little on that page to find it.

If you do this, remember to go back to the original settings in about:config. If you don't, auto updating might stay off.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 12, 2013

Just a quick thank you, Hyper, for your outstanding replies and the effort
put into them.

I'll dig into the above and hope that I have the same outcome as you, as
I'd like to stay with Firefox's latest versions. However, one of the things
I DON'T like about automatic updating of ANYTHING is that you're never
aware when something might have created a problem if you don't know when it
was updated.

Anyway, thanks again, and I'll report back with my experience.

Regards,

Neil

On Thu, Apr 11, 2013 at 9:39 PM, Hyperoptic notifications@github.comwrote:

< The value for the first item was already set to false. The entire line
was in bold type. Does this indicate that it had been changed from the
original setting (via the Tools>Options>Update panel?>

Yes

< I DID see this: app.update.enabled (no caps and the words "autoUpdate"
omitted), and its value set at "true", with the entire line in NON-bold
type. Is this the same thing you were referring to?>

Yes. Maybe my notes editor added the extra as a "correction." I can't
explain it otherwise. Any missing entry in about:config in your version as
opposed to mine may be because I have a document in Firefox's Profiles
folder called user.js where I make about:config changes. It links to
about:config and is easier to handle. The document needs occasional
updating. It goes back years, but I keep on top of it. As well, I have a
Mac, as I mentioned in a previous post, so perhaps the entries are
different in Windows.

You might check out this site to clear up some questions.

http://kb.mozillazine.org/Firefox_:_FAQs_:_About:config_Entries

Mozillazine, a group of volunteers, is not affiliated with Mozilla. The
link above goes to the about:config page in the Mozillazine Knowledge Base.
The updating options, at least most of them, depending on the age of that
article, are there.

Mozillazine also a question-and-answer forum that goes back years:

http://forums.mozillazine.org/index.php

If you go to it but it says you are banned, it's because of a forum
software bug. The ban notice includes a couple of lines saying to clear the
cache and the cookies, and try again. Apparently you're never banned if
you've signed up and log in. (I have nothing to do with that forum.)

But all this may be moot. I have since gone back to using Firefox 20.0. I
downloaded the add-on checkCompatibility that turns off old add-on
checking. I then downloaded NoSquint 2.1.6, and with compatibility checking
turned off, it works in 20.0. 2.1.6 is here:

https://addons.mozilla.org/en-US/firefox/addon/nosquint/versions/

Scroll down a little on that page to find it.

If you do this, remember to go back to the original settings in
about:config. If you don't, auto updating might stay off.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16273195
.

@Bob-SF

This comment has been minimized.

Copy link

Bob-SF commented Apr 16, 2013

I have been having the problems reported above, namely: in Firefox 20.0 on a Mac, the NoSquint 2.1.8 popup window does not close using the OK button, and does not maintain the checkbox settings when the window is exited via Cancel or the red close button. However, changes made to the size sliders are retained if the exit is made via the Cancel button (but not if the close button is used). Furthermore, whenever the OK button is used, regardless of whether a setting has been changed or not, an error message appears in the Error Console, looking like this:

Firefox error

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 16, 2013

Thanks. I think I know where the problem is happening, but I have no idea why. I've yet to be able to reproduce this problem myself.

Could everyone who's experiencing this problem please report your OS if you haven't already? Bob-SF and Hyperoptic are both using Mac. @neil49 are you using a Mac also? I'm using Linux, and if this is an OS-specific problem that could explain why I'm not able to reproduce it.

Meanwhile, I'd appreciate it if you could try this build, which is a first attempt to workaround this problem blindly:

https://www.urandom.ca/nosquint/downloads/nosquint-2.1.9a1.xpi

Thanks all.

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 16, 2013

I should add, 2.1.7 and later only work with Firefox 20+. Support for older versions was dropped, so users with Firefox 19 and older can continue using NoSquint 2.1.6.

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 16, 2013

Great job, Jason. All seems well with 2.1.9a1.

I first ran it with a virgin Firefox 20.0 after first downloading 2.1.9a1 to the desktop. I then backed up and trashed everything Firefox/Mozilla in the system, including Firefox's Profiles folder . I dragged 2.1.9a1 to an open Firefox window to load it. There were no problems setting it up or surfing the net.

I then trashed the virgin 20.0 along with everything Mozilla/Firefox in the system, including the Profiles folder, and reloaded my own 20.0 setup that at the moment is running 15 add-ons, including NoSquint 2.1.9a1. All remains well.

I uploaded to Dropbox a short screen-capture Quicktime video of 2.1.9a1 doing its thing, including through a Firefox quit and restart, without a hitch. It's here:

https://dl.dropboxusercontent.com/u/10105188/NoSquint.mov

Thank you for the fix.

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 16, 2013

I shouldn't have made that video with the theme add-on I run, Aeon 6, that uses a plain white background (and that will load into 20.0 only with add-on checking turned off). That theme bleaches the blue out of the buttons. I forgot to use the default theme for the video.

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 16, 2013

Amusingly, your screencast shows another bug: when you adjusted the zoom levels in the site settings dialog, opened global settings, then closed the global settings, notice that the zoom level of the site snapped back to the defaults even though the site dialog showed the values you just changed them to.

Here's an updated build fixing that bug. It turned out to be somewhat non-trivial so it's possible I've introduced regressions.

https://www.urandom.ca/nosquint/downloads/nosquint-2.1.9a2.xpi

@neil49, @Bob-SF I'd appreciate it if either or both of you could test this build and let me know how it goes (and as well report your OS).

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 16, 2013

Also, could you verify that things work ok with a private browsing window? Notably, site preferences should be retained as long as the browser window is open, but changes should not affect that site in other browser windows, and those changes should be discarded when the private browsing window is closed.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 17, 2013

Hi, Jason--

Sorry, I forgot to mention my OS in earlier postings.

Windows 7 Ultimate 64-bit, SP1

On Tue, Apr 16, 2013 at 8:06 AM, Jason Tackaberry
notifications@github.comwrote:

Thanks. I think I know where the problem is happening, but I have no
idea why. I've yet to be able to reproduce this problem myself.

Could everyone who's experiencing this problem please report your OS if
you haven't already? Bob-SF and Hyperoptic are both using Mac. @neil49https://github.com/neil49are you using a Mac also? I'm using Linux, and if this is an OS-specific
problem that could explain why I'm not able to reproduce it.

Meanwhile, I'd appreciate it if you could try this build, which is a first
attempt to workaround this problem blindly:

https://www.urandom.ca/nosquint/downloads/nosquint-2.1.9a1.xpi

Thanks all.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16443223
.

@neil49

This comment has been minimized.

Copy link

neil49 commented Apr 17, 2013

Hi, Jason--

Yes, following* Hyperoptics*' earlier suggestions, I have been using FF
19.0.2 with 2.1.6 for a few days now without problems, after disabling auto
update in about:config.

I intend to follow up on his further suggestion to update to FF 20 once I
have the time to double-check the recommended settings and try it out for a
while.

Neil

On Tue, Apr 16, 2013 at 12:32 PM, Jason Tackaberry <notifications@github.com

wrote:

I should add, 2.1.7 and later only work with Firefox 20+. Support for
older versions was dropped, so users with Firefox 19 and older can continue
using NoSquint 2.1.6.


Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-16459202
.

@Bob-SF

This comment has been minimized.

Copy link

Bob-SF commented Apr 17, 2013

Jason, installing 2.1.9a2 has fixed the problems I was having! Your MUCH APPRECIATED add-on now works normally again, and it does not cause error messages in the Error Console. It also works as expected in a Private Window, i.e., it enables changes in the Private Window without affecting the same site in a regular window open at the same time, and it discards the changes made in the Private Window once that window is closed. System: Late 2006 iMac running Mac OS X 10.6.8 (about to be replaced with a Late 2012 iMac running Mountain Lion).

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 17, 2013

I recorded this in a virgin Firefox 20.0 with NoSquint 2.1.9a2 the only add-on.

https://dl.dropboxusercontent.com/u/10105188/2.1.9a2.mov

A normal window is on the left; a private-browsing window is on the right.

If you'd rather I do it some other way, let me know.

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 17, 2013

Sorry. I screwed up. There was no private-browsing window in the video. I'll try it again.

@Hyperoptic

This comment has been minimized.

Copy link

Hyperoptic commented Apr 17, 2013

2.1.9a2, normal page left, private-browsing page right.

https://dl.dropboxusercontent.com/u/10105188/NS%202.1.9a2.mov

Global Settings carries over from the private-browsing page to the normal page, until NoScript is opened again on the normal page. The same happens in the other direction.

@jtackaberry

This comment has been minimized.

Copy link
Owner

jtackaberry commented Apr 17, 2013

@Hyperoptic: very nicely spotted, thanks. Third time's the charm?

https://www.urandom.ca/nosquint/downloads/nosquint-2.1.9a3.xpi

@Infocatcher

This comment has been minimized.

Copy link

Infocatcher commented May 15, 2013

I think, this may be caused by PrivateBrowsingUtils.isWindowPrivate() calls for not yet loaded window, see Infocatcher/Private_Tab#61 (comment) (and this may cause other side-effects).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment