All (well, most of) the icons for sites in my Hot Network Questions sidebar are misaligned or otherwise broken:

enter image description here

I'm seeing this on all of my devices (MacBook, iMac, iPhone), which are all using Safari. It curiously does not appear to happen on meta SE, but it does happen on every other site I've tried. It's been happening since at least last night.

I realize this issue has been reported before

but all of those issues are old (from fall 2015) and reported as fixed. Has the issue re-appeared, or am I doing something dumb on my end?

  • Can you check with Chrome/Firefox to see if it's Safari only bug? – Shadow The Princess Wizard Jul 4 '16 at 21:57
  • This happens on all sites? Different sites? Also when browsing on HTTPS? Did you try a hard refresh/clearing the caches? – Oded Jul 4 '16 at 22:03
  • This can happen either because the generated sprite sheet had a bad icon (say one 32*32 in a sheet that is all 16*16) or if the generated CSS for it is off. The issues we've had with generated files have been fixed in the past, and given that this has only been reported by yourself (with a single upvote), I suspect it is very localized. Meaning - possibly you ISP is caching a bad old file (or another cache between yourself and our CDN). – Oded Jul 4 '16 at 22:06
  • 2
    I'm seeing this with Chrome, Firefox and Safari, after clearing caches, over HTTP and HTTPS. I wrote a bug report mistakenly at meta.SO here: meta.stackoverflow.com/questions/327377/…. It isn't happening on all sites. I suspect it might be an ISP cache (I'm on Comcast in the USA). – nneonneo Jul 4 '16 at 23:47
  • Yup, my situation is the same as @nneonneo, although I didn't test Firefox. Also on Comcast, so maybe that's the problem. – user155595 Jul 5 '16 at 0:58
  • 2
    @JoshPetrie: Are you perchance in Seattle? I just checked the offending spritesheet cdn.sstatic.net/img/favicons-sprite32.png?v=deee83c5ac83. It should be 32x12276 pixels, which is what I get via wget. But, in my browser, it always comes up 32x12240 pixels. The headers indicate that a Varnish cache server in Seattle (cache-sea1924-SEA) is responsible for this. – nneonneo Jul 5 '16 at 1:30
  • 2
    Cute, it might be a Varnish bug. If I use curl -vvvvv 'https://cdn.sstatic.net/img/favicons-sprite32.png?v=deee83c5ac83' --compressed -O, I get the wrong (old) 32x12240 image; if I use curl -vvvvv 'https://cdn.sstatic.net/img/favicons-sprite32.png?v=deee83c5ac83' -O I get the right image. – nneonneo Jul 5 '16 at 1:34
  • @nneonneo Yes, I'm in Seattle. :D – user155595 Jul 5 '16 at 2:45
  • @Oded isn't this a no-repro bug? (i.e. the behavior itself as seen in the screenshot looks like a bug, but it can't be reproduced) – Shadow The Princess Wizard Jul 6 '16 at 17:54
  • @ShadowWizard - as seen by the comments, if anything, it is a bug in the proxy that comcast is using near Seattle... not really something we control or can control. – Oded Jul 6 '16 at 19:33
  • Yet another reason to use HTTPS.. – JonasCz - Reinstate Monica Jul 6 '16 at 22:22

This appears to have been resolved, I think @nneonneo's theory that it was a caching problem was correct.

  • Glad things are working now. Seemed very localized and not under the control of SE. – Oded Jul 6 '16 at 16:42

You must log in to answer this question.