789786 - Pages on blogspot.com do not render

Status: RESOLVED WORKSFORME

(Camino Graveyard :: Page Layout, defect)

Description

[Hauke Fath]

Attachment: Camino stuck at rendering myapplenewton.blogspot.com

User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.2.29pre) Gecko/20120831 Camino/2.1.3pre (like Firefox/3.6.29pre)
Build ID: 20120831001751

Steps to reproduce:

I entered a URL for a page on blogspot.com, e.g. http://myapplenewton.blogspot.com/


Actual results:

The page gets stuck at the initial display of turning cog wheels.


Expected results:

The page should have rendered. Safari does the Job just fine.

Comment 1

[Chris Lawson (gone)]

The site is slow, but it loads up fine for me if I give it some time.

Maybe try a fresh profile using Troubleshoot Camino? (Available from http://www.ardisson.org/smokey/moz/ .)

Comment 2

[Hauke Fath]

(In reply to Chris Lawson from comment #1)

The bug can be closed; sorry for the noise.

I run Camino such that it asks me before setting any cookies; and I default to "no". Turns out that the javascript mess behind blogspot doesn't take well to that, and busy-loops.

Enabling cookies for the page "fixed" the issue.

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to Hauke Fath from comment #2)
> I run Camino such that it asks me before setting any cookies; and I default
> to "no". Turns out that the javascript mess behind blogspot doesn't take
> well to that, and busy-loops.

I'd debugged this on another page before; specifically, the problem is that the site wants to use HTML localStorage (“cookies on steroids”), and, despite the fact that user-agents are supposed to treat localStorage analogous to cookies, the geniuses who implemented localStorage in Gecko reused the cookie acceptance pref to control localStorage acceptance behavior, but didn't handle all of the possible cases.  In fact, they hard-mapped "ask" to "deny"!  It's a long-standing bug which I've complained about in the past but which the Gecko developers in charge of that code seem unwilling to fix.

So, as you've discovered, allowing cookies "fixes" Google's JavaScript mess (either switching "ask" off permanently, or switching off "ask", setting the cookie, adding a cookie exception for the site, and switching "ask" back on).  It's unfortunate that both Google and Gecko are each so broken in this case.

Comment 4

[Hauke Fath]

Thanks for the explanation - since Camino does not give you an UI setting for "local storage" (Jobsian over-simplification?), I didn't have that on the radar.