ZachMatthews

I would also point out that, if you’ll read my initial post in this thread, you’ll see that this is an issue even on Admin pages, which are not in any way governed by the theme.

Yes, it is repeatable regardless of theme. Moreover, I highly doubt the others responding above all have the same theme.

With all due respect, perhaps it is time to stop trying to put us off and start taking these reports seriously?

With respect to WordPress, I don’t think this is actually a WordPress issue per se. I think it is a Chrome issue, which is demonstrated by the link I posted above where other people are having this problem with different CMSs. But that doesn’t mean it isn’t something WordPress could address.

I’m speaking with my host to see if I can modify the 304 response on the server side.

Would it help if I posted a link to a screenshot?

Took me less than 1 minute of browsing on Chrome OS x to generate it:

https://www.itinerantangler.com/temp/screenshot.png

Compare with:

https://www.itinerantangler.com/blog/board/forums/

The control-f5 may be the issue because you’re generating a hard refresh, circumnavigating the 304 response.

The problem occurs on refresh, not on the initial load. Your ability to see the site on the initial load is not reproducing the bug because you’re not spending enough time there navigating around for Chrome to need to send a refresh request and generate a 304 response.

This is independent 5X reporting on the same issue. It’s a bug.

Here’s more info in a non-wordpress context:

https://stackoverflow.com/questions/15767917/page-refresh-causes-css-to-be-ignored

And here’s a good explanation from that thread:

It turns out this has to do with chrome handling the 304 response.

Chrome asks for content and receives a 304 response saying it is not modified.

When IIS returns a 304 response it has content-type in it. Chrome doesn’t ignore the content type and looks and sees that the content type has been changed since IIS just returns the default type chrome thinks the file is no longer a stylesheet and doesn’t load it.

So in order to fix this we made it reload stylesheets everytime. I have not figured out an easy way to modify the 304 response so that it does not include content-type.

Here is the google issue https://code.google.com/p/chromium/issues/detail?id=246875

It looks to me like in the most recent WordPress build something changed with the 304 content-type setting. I am not sure how we can modify that but the solution for now seems to be making our servers not return a content-type setting of any kind on the 304 response. That may be a server-side issue.

Here’s more info in a non-wordpress context:

https://stackoverflow.com/questions/15767917/page-refresh-causes-css-to-be-ignored

This is happening on my site as well and seems to be related to Chrome failing to ignore something in the 304-no change response from the server. Firefox and other browsers do ignore this bugged setting, which I think has to do with content-level or something like that. I’ll try to find more details and consolidate, but this is a serious bug in the new WordPress build with respect to Chrome users.

PS here’s a link to the forum:

https://www.itinerantangler.com/blog/board/forums/

Looks like I may have been confusing your plug in with the bbPress Unread Posts plug in. My apologies.

Ok, now that you show me that link I see that we do have the Mark as Read link going in the individual thread section. Was there not a ‘Mark ALL as Read’ feature as well that showed on the topics page? Or was that another plug in?

Man, I just plain old have no button to push. It’s supposed to be right by the Subscribe link, right? Where is your plug-in injecting that link? Into page.php maybe? I can go check my template and make sure it’s not overriding it.

I believe that’s what happened, yes. I can turn your plug in on but I have no button to push. I’m simultaneously using another plug in to light up which posts have been read, but that one never had the ability to ‘mark all read.’

Here’s the site if you want to take a look: https://www.itinerantangler.com/blog/board/forums/

If you guys will go look here, what I wound up doing is leaving it in .onecol (the default), abandoning the sidebars, and tweaking the CSS.

https://www.itinerantangler.com/blog/board/forums/

If you do a multi-site you can limit this setup to one page only (i.e. the forum) and still have a fully-functioning Pinboard theme elsewhere. I’ve integrated everything under one “roof” even though I am actually running three separate multisite Pinboard instances. It looks good, not too awkward to manage since you just end up having three separate admin pages (which are all integrated under the dropdown top tabs on the /admin/ home page for the whole site).

Zach

Use Chrome and download the Chrome extension DevTools. Then use the ‘inspect element’ option to examine the CSS of whatever you want to change. You can then add the changes to the Theme Options/Layout page and they will auto-magically appear last in the CSS stack and thus edit the code. This is basically a built-in way of making a child theme’s stylesheet.