-
Problem report
-
Resolution: Won't fix
-
Trivial
-
None
-
None
-
None
-
Sprint 50 (Mar 2019), Sprint 51 (Apr 2019), Sprint 52 (May 2019)
Every time after frontend upgrade you have to do Ctrl + Shift + R to force reload of static content cached by the browser. Experience users remember to do this when the suspect broken layout after upgrade but you can't expect this from all users and TV screens in a large organisation.
How about introducing versioning of affected CSS, javascript, image etc file names (e.g. styles/dark-theme_v401.css) which change upon every upgrade thus forcing the browsers to reload them automatically?
