@media only screen and (-webkit-min-device-pixel-ratio: 2), only screen and (min-device-pixel-ratio: 2) {
.votearrow { background-size: 10px; background-image: url("grayarrow2x.gif"); }
}
.rotate180 {
-webkit-transform: rotate(180deg); /* Chrome and other webkit browsers */
…
It wasn't like that before, there were only gray{arrow,down}.gifForced refresh should help.
/* 13.328px = 1em */
.votearrow[title=upvote] {
background: none !important;
}
.votearrow[title=upvote]:after {
content: '';
display: block;
position: relative;
top: -1px;
width: 0;
height: 0;
border: .3em solid transparent;
border-bottom: .6em solid #999;
}Would be nice if the favicon was similarly updated.
Was having that problem, changed that, and it worked.
<link rel="stylesheet" type="text/css" href="news.css?1382794165">
If it always forces re-fetch, then an alternative is to bake the timestamp or hash into the filename (so news-1382794165.css), and update the html generation to point to the new timestamp/hashed file name. Then the browser will fetch newly generated css (etc) exactly once (modulo cache eviction/clearing), and without a force-refresh.
You rewrite all /Static/<vXX>/* URLs on the serverside to /Static/*. You could create a helper function which inserts the version number in URLs for static files, and use relative paths for images in the CSS file.
I don't like "Css" though. If it's an acronym it should either be all capitalized or all non-capitalized.
slinks off into the shadows
[0] Might be an option in the dev-tools settings, but I think it's enabled by default.
[1] Except when it's not, of course.
But if I am on a site that seems to be loading the old cached stuff during my regular browsing of the internet (not building stuff) I always open dev tools and refresh to do a "hard" refresh.
But learning that CTRL-F5 does the same thing is really neat, and I feel very silly at the same time!
How to fix it?
<link rel="stylesheet" type="text/css" href="news.css?1382794165">
Copy-Paste the above into your address bar & Reload HN. The new CSS file will be Rendered and issue fixed.
Hope that helps. :)
I normally append "?v=1.5" to my css and javascript files to allow for easy cache updating. Then just manually increase the version when you've made changes.
Someone enlighten me please
Is it the result of HN becoming more popular? More readers and same size front page means more readers per post, so more votes per post, so an individual accumulates karma more quickly?
or whatever you do to refresh.