InformAction Forums

It appears to be responsible for jamming up page elements on the front page only. Happening with all page scripts allowed or not and when the page has fully loaded.

With NS disabled








With NS enabled

Are there FONT objects to be allowed in the "Blocked Objects" NoScript submenu?

Giorgio Maone wrote:Are there FONT objects to be allowed in the "Blocked Objects" NoScript submenu?

If this is what you mean, no. And not seeing any Font objects when the two top domain scripts are allowed.



Could it be anything in Options>Embeddings?

I'm not seeing the issue.

If you disable all other extensions except for NoScript, does the issue persist?

As a test, if you create a new, clean Profile & only install NoScript, does the issue persist?

kukla wrote:

Giorgio Maone wrote:Are there FONT objects to be allowed in the "Blocked Objects" NoScript submenu?

If this is what you mean, no. And not seeing any Font objects when the two top domain scripts are allowed.

Look closer.
As soon as I allow "nytimes.com" I get a new Blocked Objects>Temporarily allow FONT@http://www.nytmes.com menu item.
Beside that, the typeface is the main difference between the two screenshot you posted.
As a side note, I didn't manage to stuff all those characters all together, no matter the zoom level I used: it must be a Mac OS X - specific issue, related to the default replacement font Firefox uses on that platform (I've tested on Windows).

Mozillazine thread for reference, nytimes.com front page.

Giorgio Maone wrote:

kukla wrote:

Giorgio Maone wrote:Are there FONT objects to be allowed in the "Blocked Objects" NoScript submenu?

If this is what you mean, no. And not seeing any Font objects when the two top domain scripts are allowed.

Look closer.
As soon as I allow "nytimes.com" I get a new Blocked Objects>Temporarily allow FONT@http://www.nytmes.com menu item.
Beside that, the typeface is the main difference between the two screenshot you posted.
As a side note, I didn't manage to stuff all those characters all together, no matter the zoom level I used: it must be a Mac OS X - specific issue, related to the default replacement font Firefox uses on that platform (I've tested on Windows).

Yep, I'm seeing that now, and after allowing it things get straightened out. I also tried a new temporary profile, with only NS installed, from therube's suggestion, and it's not happening there with both of those top scripts not allowed. So it's some kind of conflict with another Add-on. Honestly, I don't think it's worth all the trouble to get completely crazy and drill down to which Add-on is causing the conflict. I think I will just have to live with it, since I don't usually allow any scripts from the Times anyway.

But it is odd that it appears to have started only with the NS update, but of course that might only be coincidental with some change the Times made to its front page CSS. Even with some elements jammed up, it's still readable.

The solution actually had nothing to do with an add-on conflict (and sorry to have thought ill of NoScript ): I discovered finally that the Tmes front page suddenly wasn't happy with a minimum font of anything more than 12.