736917 - Bloomberg futures page content is blank with ad-blocking enabled

Status: RESOLVED FIXED

(Camino Graveyard :: Annoyance Blocking, defect)

Description

[[e-mail]]

Attachment: Camino 2.1.2 Bloomberg Page display.jpg

User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.2.28) Gecko/20120308 Camino/2.1.2 (like Firefox/3.6.28)
Build ID: 20120308211433

Steps to reproduce:

I went to the Bloomberg stock futures page. 

Here is the URL:

http://www.bloomberg.com/markets/stocks_v2/futures/




Actual results:

My newest version of Camino 2.1.2 does not display the data on the page.

Safari displays the page perfectly.


Expected results:

The stock futures data should have displayed in the center of the page. Please try it for me.

Thanks,

Jerry South

Comment 1

[philippe (part-time)]

It is caused by ad-blocking. The bloomberg people had the weird idea to wrap the content inside a div with class="market_content_with_right_ad"…

You can work around this on your side by opening user_ad_blocking.css in a plain text editor (located inside your profile: ~/Library/Application Support/Camino/Chrome) and add the following at the bottom of the file: 

@-moz-document domain(bloomberg.com) {
div[class="market_content_with_right_ad"] {display:block !important; }
}

Then from Camino preferences > Web Features, toggle 'Block web advertising' off and back on.

Comment 2

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

We should add that override rule to the default overrides in the next omnibus ad-blocking update.  Stupid sites :/

Comment 3

[[e-mail]]

Phillipe's prescription worked perfectly for me.  The futures are now appearing.
  
Nice workaround fix. I hope I don't run into another one.

Thanks a lot.  You guys are super helpful.

Jerry South

Comment 4

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

--> philippe, since he wrote the rule I pasted into the file ;)

Comment 5

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

Fixed by the checkin for bug 687017.