[UNRELATED] Firefox 14 Problems

[Quite Puzzled]

Two problems with NoScript, including 2,4,9rc1 and Firefox 14, problems that did not arise with Firefox 13.x and earlier versions:

1. When NoScript is active, Readabilty will not work, neither the extension nor the bookmarklet. www. readability.com , www.readability.com/bookmarklets.Disabling NoScript on the desired page does not help, I have to disable NoScript and restart Firefox.

2. Similarly, videos at http://www.youtube.com/JustPlanes don't appear. Curiously, although I cannot see them, I can download them. (With NoScript disabled, I can see the videos, although they are in what is to me a strange form, which may have always been there; as I had never visited the site without NoScript running, I don't know if the odd format, with the video off to the right in a small box, and a right-click pop-up option for a full-screen view has always been the case for this site.)

[therube]

Youtube looks to be working fine.
Clip I looked at was HTML5. (Yesterday Youtube was having all kinds of troubles with HTML5 giving non-responsive script warnings in browsers.)

[Quite Puzzled]

Youtube looks to be working fine.
Clip I looked at was HTML5. (Yesterday Youtube was having all kinds of troubles with HTML5 giving non-responsive script warnings in browsers.)

Curiously, I had no YouTube problems yesterday; I went directly to YouTube when I encountered the Just Planes difficulty, and there YouTube was fine, but the latter persists for me as of a few minutes ago. I saw quite a lot of YouTube problem-related traffic on MozillaZine yesterday and today, so was aware that YouTube itself was not working correctly; however, I, being me, and therefore contrary, did not encounter the reported problems, but found my own.

[Quite Puzzled]

1. I recently installed NoSquint to fix the problem of sites that don't recognize wide-screen monitors and, therefore, jumble some of their text. Having realized that, I returned to JustPlanes, reduced the default setting from 105% to 100%, whereupon the usual NoScript blocking icon appeared, which I clicked on, and saw a video. I then went to a second video clip, had a bit of difficulty in getting it to work properly, but did succeed in viewing it. I don't know for certain if this problem was there after installing NoSquint but before installing Firefox 14.0.1; I don't think so, I suspect it arose with 14.0.1, but as I can once again view JustPlane clips, all is well. (As an aside, I finished watching my latest purchase from them yesterday, one of their new Blu_Ray discs.)

2. I then went to http://www.sundayriverproductions.com/ , to take a look at a few of their clips. Clips show up, but instead of clicking on the NoScript icon, I found that right-clicking on the video caused it to open in a new tab (as it supposed to,) and can be viewed.

3. Earlier today, I got a thank-you note from Readability, thanking me for my feedback on the problem(s), so I can only assume that they will be pursuing this.

4. And, of course, one must not to forget to mention "everything else...".

[Quite PUzzled]

And here is the 'everything else: While I was getting out dishes, etc., prior to cooking dinner, I wondered if reducing an apparently-blank Readability-treated page from 105% to 100% would have any effect. Answer: The page becomes visible.

I know for certain, unlike with JustPlanes, that this is a change engendered with Firefox 14.01, as 105% worked correctly with Firefox 13.0.1. I shall report this to Readability.com.

[Quite Puzzled]

I note that this thread has been marked as unrelated. I don't have a problem with that, but please allow me to explain why I started it: When I started encountering the problems that I have listed in the thread, I went through the normal troubleshooting process for Firefox, namely disabling sets of extensions until the problem stopped. In doing that, I found that the problem(s) went away when I disabled NoScript, so it seemed reasonable to conclude that the problem lay with that specific extension.

This is the first time in the many years of using Firefox that I have encountered a situation wherein the apparent cause of an extension problem, in this case NoScript, turned out to not be the actual cause of the problem. Why disabling NoScript seemed to remedy the situation when it was actually caused by the next extension alphabetically in my set of extensions, NoSquint, is quite beyond my comprehension.