Display issue with Project/speech titles (browser specific)

Hello, multiple users have reported seeing an issue with our site where the speech title (whether populated or blank) is 'replaced' with the text "Evaluations are what we are here for". I think this was a speech title that was given many weeks ago, but I am unclear as to how or why it is replicating into the agenda each week. This issue is specific to Google Chrome, I have attached a screenshot of Chrome on the left and Microsoft Edge on the right. Note: the screenshot show's members who have not input the manual/speech nor set a title, but the issue occurs even if that has been done, the text is overwritten moments after the page loads. To make things even more strange, I am not able to reproduce this issue consistently. For example, it was happening yesterday, but today it is not.

Are there cookies or a cache I should clear somewhere? Could it be saved into the agenda somehow? Is this a known issue? Thank you for any help or advice!

Justin
Cerner PowerSpeakIT #793002

Well, we need to be able to reproduce it to fix it.

I will not do any kind of changes that are just "wild stabs in the dark".

Understandable. I'm perplexed by it being seen and reported by multiple users on different (corporate) computers, with Chrome being the consistent browser. Is there a cache that I should clear, or anything else? I'm at a complete loss as to why the issue is sporadic... are there multiple servers hosting FTH, could it potentially be narrowed down to one troublesome box? I followed the same steps today as I did yesterday when I was seeing the issue, and today it's not happening.

There is your clue

(corporate) computers

Are you using a caching proxy server at work? Most companies do. That will be your culprit.
Try clicking the reload at the bottom of your site and see it it stays.

Done! I'll send a message to our club DL instructing them to do the same. I'll report back if we see the issue again. Thank you both!

Well Chrome does aggressively cache a lot of stuff... that is one of reasons it tends to be a fast browser.

However, unless it is incorrectly classifying these fields as autocomplete / form fill fields, I would not consider that information to be typical of what I would expect Chrome to cache. Most stuff that gets cached are the things that slow down web page loading... e.g. pictures, scripts, etc. downloaded from the server. Single fields are nothing in the big scheme of things, so I would not expect caching to be the issue unless there is an errant script populating those fields.

Note also that I have been tinkering with the code around the edges... It is possible that you got some "not fully cooked" code while I was doing changes... All those changes are done now, though.

I would say keep an eye on this and look for patterns of use/trends to see if you can come up with a way to reproduce the issue. Some things to pay attention to:

1. Does it only happen on agenda initial load or after an edit?
2. Does it happen after someone takes or drops a role via the button? What if you add/drop via the agenda editor?
3. Anything in common about the roles?
4. Are there any Javascript errors in red in the Chrome Developer Console?