533112 - Camino will not display the comments from bloggers on the Sacramento Bee

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: General, defect)

Description

[Patrick Barber]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en; rv:1.9.0.16) Gecko/2009120123 Camino/2.0.1 (like Firefox/3.0.16)
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en; rv:1.9.0.16) Gecko/2009120123 Camino/2.0.1 (like Firefox/3.0.16)

The bloggers comments appear when I use Opera, but not Camino does not.  It is not reading or identifying all of the possible data.  Very frustrating.

Reproducible: Always

Steps to Reproduce:
1.It happens every time on news articles on the websites
2.
3.

Comment 1

[Chris Lawson (gone)]

Without a URL, there's probably not much we can do here. I'm going to take a wild guess that the Sac Bee didn't design their site solely for Opera, so I bet this is an ad-blocking issue. You should check with Firefox 3.0.x just to be certain, though.

If you turn off ad-blocking, does the problem go away?

Please don't change the Priority flag (or anything else like that); those are really more for developer use.

Comment 3

[Chris Lawson (gone)]

I've tried this with a nightly (2009111600) and with the 2.0.1 release with both my normal profile and a clean profile, and the only way I can get the comments to disappear is to click the "Hide comments on sacbee.com" button just above the comments. Once that's clicked, the button changes to a "Show comments on sacbee.com" button, and clicking it brings the comments back. Having ad blocking on or off makes no difference.

You should probably clear all your cookies from sacbee.com and try again.

Comment 4

[Chris Lawson (gone)]

To be perfectly clear: if you clear all your sacbee.com cookies and try again, does that fix the problem?

Comment 5

[Chris Lawson (gone)]

Patrick, can you please answer comment 4?

Comment 6

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

Closing INCOMPLETE due to lack of updates.  If the problem still exists in Camino 2.0.1 or a recent nightly and you can supply the requested additional information, you may reopen this bug.