5

In Firefox, the topbar icons aren't showing (it's just black there). I looked at the CSS, and the new style is

background-image: url('../img/share-sprite-new.svg?v=2d10b452229b'),none;

Changing it to

background-image: url('../img/share-sprite-new.png?v=2d10b452229b');

worked, but with the SVG, it wouldn't load.

  • I've heard another report of this in Chrome. I haven't been able to reproduce. – Adam Lear Nov 14 '14 at 6:41
  • 1
    This seems to be happening with a specific list subscription using adblock plus. – Oded Nov 14 '14 at 8:05
  • @Oded: Confirmed. I have Chrome 38.0.2125.111 on Windows 8, and the topbar images disappeared yesterday. I disabled Adblock Plus and now they're back. – El'endia Starman Nov 14 '14 at 12:45
2

Topbar Blocked by AdBlock Plus Using the Fanboy Annoyances List

I was having the same problem, and @Oded's comments helped me track it down. The problem is that https://meta.stackexchange.com/content/img/share-sprite-new.svg?v=2d10b452229b triggers on /share-sprite- from the Fanboy Annoyances List in AdBlock Plus.

I've outlined two ways to fix this, but there are certainly others. Your mileage may vary.

Disable Filter

To fix it, you can use Ctrl+Shift+V and click the red x to disable that filter altogether. This applies to all sites, not just StackExchange.

Create Filter Exception

Alternatively, you can open the Adblock Plus preferences with Ctrl+Shift+F and create a custom filter with finer-grained permissions that apply just to the StackExchange network and its CDN. For example:

@@/(stack(exchange|overflow)|sstatic).*sprite/

There may be a more efficient way to specify the exception, as AdBlock Plus will mark this exception rule with a snail, but it will certainly get the job done. Your mileage with custom filters and regular expressions will certainly vary.

| improve this answer | |
  • It worked on Meta, but not elsewhere. I thing the general principle is sound (i.e. Adblock), but why isn't it working elsewhere? – cpast Nov 15 '14 at 22:32
  • 1
    @cpast Some StackExchange assets use cdn.sstatic.com as their CDN, so the filter exception might not trigger. @@/(stack(exchange|overflow)|sstatic).*sprite/ will work better across more SE sites, but it may still miss assets on some sites. YMMV. – CodeGnome Nov 15 '14 at 22:47

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .