tag:tenfourfox.tenderapp.com,2012-01-07:/discussions/problems/7819-new-york-times-fonts-againTenFourFox: Discussion 2016-02-12T07:50:35Ztag:tenfourfox.tenderapp.com,2012-01-07:Comment/391377502016-02-10T15:55:24Z2016-02-10T15:55:24ZNew York Times Fonts Again?<div><p>Confirmed on 10.5. The browser doesn't recover from the spinning
beachball, with RAM usage steadily increasing. It went up to 1.5 GB
within a few minutes and then crashed. It doesn't seem to be
downloadable fonts. Still locks up with ion and/or baseline
disabled, but I didn't wait for it to crash here. Doesn't lock up
with JS disabled completely, but then website functionality is
reduced. Safari 5 works ok.</p></div>Chris (chtrusch)tag:tenfourfox.tenderapp.com,2012-01-07:Comment/391377502016-02-10T16:19:06Z2016-02-10T16:19:06ZNew York Times Fonts Again?<div><p>The offending script is likely to be hosted at <a href="http://graphics8.nytimes.com">http://graphics8.nytimes.com</a>. If
I disable JS for this subdomain only the site loads fine.</p>
<p>That said, some headings on the site are displayed as boxed As,
fallback works only if downloadable fonts are disabled.</p></div>Chris (chtrusch)tag:tenfourfox.tenderapp.com,2012-01-07:Comment/391377502016-02-10T17:59:22Z2016-02-10T17:59:23ZNew York Times Fonts Again?<div><p>I can confirm that the nytimes.com site loads without crashing
TenFourFox if javascript is disabled. But I do not know how to
disable javascript for a single subdomain so I have not tested
that.</p></div>Iain Harristag:tenfourfox.tenderapp.com,2012-01-07:Comment/391377502016-02-10T18:39:32Z2016-02-10T18:39:33ZNew York Times Fonts Again?<div><p>I just tried turning off javascript for the <a href="http://graphics8.nytimes.com/">http://graphics8.nytimes.com/</a>
domain only, using YesScript, and that did solve the problem.</p>
<p>Thanks for that!</p></div>Iain Harristag:tenfourfox.tenderapp.com,2012-01-07:Comment/391377502016-02-12T00:45:43Z2016-02-12T00:45:43ZNew York Times Fonts Again?<div><p>I've finally analyzed this issue, and it does appear to simply
be another font that needs to be blacklisted (more accurately it's
the same font, but the NYT moved them to a different URL, and we
have to use a URL-based block for this because it does not have a
proper PostScript name). The reason blocking the script works is
because it creates a DOM node that loads the offending font. With
the blacklist fixed, I am no longer able to reproduce this
issue.</p>
<p>The updated blacklist is scheduled for 38.6.1, which is an
imminent update to fix an urgent Firefox security issue.</p></div>Cameron Kaisertag:tenfourfox.tenderapp.com,2012-01-07:Comment/391377502016-02-12T07:50:34Z2016-02-12T07:50:34ZNew York Times Fonts Again?<div><p>I'm not sure. When I tested it, the problem persisted even with
downloadable fonts disabled. Today I'm unable to reproduce it with
38.6.0 in the first place (fresh profile, downloadable fonts
enabled, no blockings). I guess nytimes.com must have changed
something. Either way it's fixed.</p></div>Chris (chtrusch)