Improve documentation around disabling browser caching

[tim-schilling]

With the backwards incompatible change in JS that was introduced in v5 or v6, we've had several issues opened and I've received at least one DM asking how to solve it. We do document in the tips area that the browser caches things, but it's the third paragraph in the section. I think adding a header to make it stand out more will help.

[developerarhan]

Hi! I'd like to work on improving this documentation.

I've reviewed the current docs/tips.rst file and noticed that the browser caching information is mentioned in the third paragraph of the "The toolbar isn't displayed!" section, but it lacks a clear heading and can be easy to miss.

Proposed approach:

Add a new section titled "Toolbar not updating after upgrade?" immediately after the "The toolbar isn't displayed!" section. This new section would:

1. Explicitly mention v5/v6 upgrades as a common trigger
2. Explain why this happens (browsers cache JavaScript/CSS files)
3. Provide specific solutions:
   • Hard refresh with keyboard shortcuts for different OS
   • Clear browser cache
   • Disable cache in DevTools
4. Help users identify the issue (e.g., JavaScript errors in the console)

This will make the information much more visible and reduce duplicate issues about this common problem.

Does this approach sound good? I'm happy to adjust based on your feedback!

[tim-schilling]

Hi @developerarhan I've already submitted a PR to try to improve this, #2302.

[developerarhan]

Thanks for letting me know, @tim-schilling !

I looked at PR #2302 - the network panel tip is a helpful addition! This was a great learning opportunity for me as a new contributor.

I'll look for other issues to help with. Thanks again!