Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Sponsor logos no longer displaying in footer #524

Closed
stevenhaddox opened this Issue · 6 comments

4 participants

@stevenhaddox

During some of the recent changes (I'm guessing?) the sponsor logos stopped displaying properly.
Screen Shot 2013-02-02 at 6 23 20 PM

This is happening in the latest version of Chrome for me on OS X. Firefox apparently seems to get images, although they're slightly mis-aligned (about half an image below the text instead of centered on it). Safari seems to be displaying everything properly as far as displaying the images and the positioning of those images.

@envygeeks
Collaborator

Are you sure it's not a caching problem? What version of Chrome? Because Chrome 24 displays them for me.

@stevenhaddox

@envygeeks: My Chrome version is: 24.0.1312.57

I saw several people talking about this issue in #rubygems-aws on IRC yesterday / today so I assumed it was proabably more than just myself, but I could be wrong. I've definitely done hard refreshes, purged cache, etc. on my end, but I'd love to be wrong.

@stevenhaddox

@envygeeks I figured out why it isn't showing up for me. Apparently some Chrome plugin is causing the issue. Once I went into private browsing mode it loaded the images load just fine. This also explains why it didn't matter how specific my CSS was to override it and it wouldn't take effect. Sorry for wasting everyone's time.

@hron84

@stevenhaddox did you figured out what plugin causes this? I experience same issue with rubygems.org ...

Plus, could you please make the "XX by" strings to link? It would be improve the accessibility of the page...

@dwradcliffe
Owner

@hron84 Send a pull request for the links and we can take a look :)

@stevenhaddox

@hron84 I think it was AdBlockPlus or similar. I'm not often on the system I encountered this with over that weekend and I forgot I had it installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.