Forum: Bug Report and Feature Requests

I have the Classic theme selected (because I find it easier to scan), and sometimes the site shows me a stories list page without applying the theme. (For example, there are no boxes around any of the stories, and the data is laid out in a different format than I am used to.)

When that happens, it's usually very difficult for me to force the site to show me the page in the Classic theme (many iterations of Force Reload in Chrome). But if I'm looking at (for example) the New Stories page, it usually corrects itself when I go to another page, but when I come back to the original page it will remain broken. This used to happen once in a blue moon, but recently it has been happening multiple times each week.

I'm using the latest version of Chrome.

Noticed similar behaviour myself.
Win10, using Edge (latest version).

It's your site, so you can do what you want. But I am convinced that it is not a problem with my browser.

After seeing the problem again, I used Chrome's Inspector to see all the files that were downloaded on the stories page, and downloaded them to examine them. The HTML code for stories list on the broken page is completely different from the HTML code for the stories list on the working page. (After downloading the broken page, I refreshed until I got the working page.)

The working classic theme page uses a table (with appropriate tr and td elements) to display the list of stories. The broken page uses an unordered list (with an li element for each story and div elements inside).

I then edited the downloaded web pages to look for t-classic3.css in the current directory, then viewed the broken page in Safari and Firefox, and both rendered it pretty much the same as Chrome. The working page rendered as expected. So the web server is definitely sending the wrong HTML when this problem occurs. (If I had to guess, it's sending the html that is designed to work with one of the other themes.) I have no idea why it never occurs for you with Firefox, but I personally don't believe that Chrome has anything to do with it. (The fact that Grant sees the problem in Edge isn't conclusive, since Edge uses Chromium.) If you want me to zip up the downloaded files to send to you, let me know.