{"items": [{"author": "Todd", "source_link": "https://plus.google.com/112947709146257842066", "anchor": "gp-1373562369182", "service": "gp", "text": "I've seen this behavior from Firefox sometimes on really slow connections (not the button, obviously). I'm not sure what triggers it, exactly.", "timestamp": 1373562369}, {"author": "Marcus", "source_link": "https://plus.google.com/115811589251174483775", "anchor": "gp-1373562944918", "service": "gp", "text": "Me too. Mostly on the New York Times website.", "timestamp": 1373562944}, {"author": "Ivan", "source_link": "https://plus.google.com/101147004225363019038", "anchor": "gp-1373563801205", "service": "gp", "text": "i have also seen Firefox do this, but there's no principled reason why others shouldn't implement it too. \u00a0in the past, text-only rendering of many websites might have been useless or ugly. \u00a0with the rise of web developers adopting web standards and progressive enhancement / graceful degradation, much of the web is actually reasonably usable without heavyweight objects (images, videos, etc.) or even stylesheets.", "timestamp": 1373563801}, {"author": "Jeff Kaufman", "source_link": "https://plus.google.com/103013777355236494008", "anchor": "gp-1373571487470", "service": "gp", "text": "I think browsers currently do this only when a request for css or js times out. \u00a0I want to be more aggressive about painting but not shorten any timeouts.", "timestamp": 1373571487}]}