3

Icons for MSE, SO, Programmers look like messed up in user profile. Am I only one observing this?

Below is example screen shot showing messed up icons in this user profile to the left and as a reference the correct icons as they appear in network profile for the same user to the right:

enter image description here

  • What browser? I'm not seeing this at all. – Taryn Aug 23 '16 at 23:37
  • @bluefeet FF 48.0, MS Edge 11.545.10586.0, Chrome 52.0.2743.116 m, IE 11.545.10586.0 on Win10 – gnat Aug 23 '16 at 23:44
  • ...though maybe Puzzling icon for Programmers is okay, it can be a part of new site name and scope changes – gnat Aug 23 '16 at 23:51
  • Am I the only one who sees your image covering up the related and hot network questions on the right? i.stack.imgur.com/weGk6.png – zondo Aug 24 '16 at 0:20
  • @zondo i observed similar effect with some browsers and OSes. I don't see it now, so you maybe tell your – gnat Aug 24 '16 at 0:21
  • I'm using Firefox 45.3.0 on Linux Mint 17. – zondo Aug 24 '16 at 0:23
  • @zondo is that the latest version you can use? I think my FF did something weird at version 47 and iirc 46. In the same time, Chrome and IE 11 worked well. It wasn't on Linux though – gnat Aug 24 '16 at 0:26
  • Interesting. Firefox 47 doesn't have a problem for me. – zondo Aug 24 '16 at 0:28
  • 1
    Problem appears for me too. Favicons are selected based on y-index from the icons "mega image". Looks like SE have added another site somewhere in the list, which caused all the icons below it to shift 32 pixels, which means that affected sites appear as the icon 32 pixels below them in the "mega image". In the case of your screenshots, Puzzling.SE icon is 32 pixels below Programmers.SE. – Adi Aug 24 '16 at 1:44
  • 1
    @Adam wrong dupe. This is the actual duplicate: meta.stackexchange.com/questions/281519/site-icons-misplaced (it's most likely another Varnish cache issue) – Shadow9 Aug 24 '16 at 13:02
  • 1
    Huh! So you're being served a different Sprites, while the CSS which contain the positions is new. This explains the mis-position. I'm afraid the only solution is for a dev to purge that varnish. – Shadow9 Aug 24 '16 at 13:16
  • 1
    @ShadowWizard Yep, it's the same issue... see my answer/comments on the dupe. – Adam Lear Aug 24 '16 at 14:44
  • 1
    @gnat Excellent, thanks for confirming. – Adam Lear Aug 24 '16 at 17:12
  • 1
    @Adam thanks, though I still don't get what's going on with that Varnish cache. – Shadow9 Aug 24 '16 at 17:41
  • 1
    @Quassnoi I'm not SE developer, just ordinary user like you, baffled by mysterious caches. (Or did you mean to ping Adam?) – Shadow9 Aug 24 '16 at 21:39

Browse other questions tagged .